Maven is a total pain. I use it grudgingly because it gets the job done. Mercurial is actually pleasant to use.



I don't know. I wouldn't mind being able to contribute fixes, enhance documentation, etc. I think most people would agree that MigLayout is already very feature-rich so I don't think committers would have such an easy time arguing that new features aren't already covered by existing ones. Anyway, it's your project at the end of the day so you get to say what goes in or not. If they don't like it they could always fork and add new features there.

On a related note, I found another example of a cell growing unexpectedly. Can you please explain why the bottom left cell insists on maintaining the same width as the bottom right? How can I get the bottom right to eat up more space?

Thanks,
Gili

The push in the spanned component will be set to the first column.

If you want to set it up in a Mercurial environment in a way that also commits maven artifacts to some central repo I'll happily make that the main branch. I would still would like to have the last say on what goes in and not of course.

Ah! Moving the push() from the top component to the bottom-right one fixed it for me. Thanks!

Is it possible to document this behavior in the cheatsheet/Javadoc? Currently there is no indication that span() causes the component's other constraints to apply only to the first cell.



I'll give this a try and let you know once it's ready.

Gili

Michael,

I have posted the Mercurial repository at https://bitbucket.org/cowwoc/miglayout/. Assuming you use Windows, I recommend using http://tortoisehg.bitbucket.org/ to pull down a copy. You will need to add the following repository to your Maven settings.xml file:

<repository>
<id>eclipse-repository</id>
<name>Eclipse Testing repository</name>
<url>http://maven.eclipse.org/nexus/content/repositories/testing/</url>
</repository>

Let me know if you need me to elaborate on how to add it. This version retains the ftp username/password in etc/pwprops.properties but we should move this into settings.xml in the near future to avoid exposing confidential information to the outside world. Please note that you will need Maven 3.x to build this project so if you're using version 2.0 you will need to upgrade.

I recommend using Google Code or BitBucket for painless repository hosting. Alternatively, you can configure your own server: http://mercurial.selenic.com/wiki/PublishingRepositories

Please let me know if you have any questions.

Gili

Ok. Hmm, I see work here. Maven 2.0 -> 3.0 for instance. I've had nothing but headaches from Maven and wasted many many hours trying to keep it working over time. The docs for Maven is effking nonexistent. All there is is obvious things but the things you want to know is left out.

I have as indicated earlier very little time over for this project since it doesn't give anything back atm. If you want to take the latest code (which I have on the HD) and upload it and set it up in miglayout's name, including all the plumbing for everything as it works today then I'm fine with it, but I can't do much myself to get it there.

Cheers,
Mikael

Okay, I'll spend time putting the project on Google Code and updating the Maven script to make it simple to publish artifacts to the central repository. I'm also busy with my own projects so this will take some time.

What specific problems do you have with the existing Maven script?

Gili

The script is working now, or did at the last try..

One problem was that it should use retrotranslator to also make a 1.4 version but I think it's time to let 1.4 go now and make everything 1.5+. What do you think? I also had a lot of problems finding an FTP wagon that worked and could upload a version to my NAS.

Something I'm still not sure if its working is that the version should be in the manifest file.

Can I send you the latest version? It's not a lot of changes but a few. Mostly spelling errors in the javadocs and such and one bug fix.

Cheers,
Mikael

I'd suggest running a poll regarding 1.4 support. I'd personally jump straight to 1.6 but I've never been very big on backwards-compatibility so I'm not necessarily the right person to ask.

Regarding uploading to the NAS, I recommend you link to Maven central instead of hosting the release files yourself. If you want to host SNAPSHOT files I'd recommend the use of Hudson/Jenkins to check out the code and host the SNAPSHOT files on your behalf.

Adding stuff into the manifest file is extremely easy. Just let me know what exact format you had in mind and I'll add it.

Let's fix all these things first and then I'll send you a built copy.

Gili

Hello,

Sorry for the delay. Not sure if you're aware of my day job but I'm currently abroad fighting injustice in the northern Africa..

1.5 is quite fine I think. There are no major advantages between 1.5 and 1.6 that we can use.

All the other stuff needs to be postponed until I get back which should be in about a month, give or take.

Cheers,
Mikael

I thought this was a joke until I checked your LinkedIn account. What is Sweden doing in northern Africa? I wasn't aware anything was going on.

Gili

Yeah, it's kind of an odd combination..

Khadaffi@Libya.

Ah. Keep up the good work!

Gili