just one line: mvn eclipse:eclipse -DdownloadSources=true
and you'll see how sources and javadocs are downloaded and linked in eclipse project maven makes: acegi-security-1.0.1.jar binaries acegi-security-1.0.1-sources.jar sources acegi-security-1.0.1-javadoc.jar javadocs I think it'll be good to keep this. And if you run the previous line in a multiproject it will link the subprojects between themselves, eg. in the top level acegi dir On 8/28/06, Ben Alex <[EMAIL PROTECTED]> wrote: > Luke Taylor wrote: > > On the branching front, it seems like we could be making more use of > > branches with subversion. > > I am happy for these changes to be made. Whilst changing to Maven 2 we > should also give consideration to how we distribute source code for IDE > integration. At present we release a separate ZIP file containing the > sources (which is not intended for compilation). I noticed that the > Maven 2 approach appears to be a <name-of-artifact>-sources.jar file in > the standard "jar" repository. > > Whilst I see merit in the above approach, I am not particularly fond of > it because I still have to undertake the manual step of configuring > Eclipse to look at a particular source JAR or ZIP. In addition, as new > releases are made, it is not uncommon to forget to change the old source > code attachment location. So your source code appears to be for say > release 2.0 but it is really for 1.2.7. I am also unaware if Maven 2 can > be made to automatically understand it needs to download source > artifacts but not include them as classpath resources. > > Those of you who have been using Google Web Toolkit (GWT) would know > Google bundles both source code and compiled class files into the same > JAR. This saves the manual step and I have found it extremely useful. I > just point to the new release JAR and my JavaDocs and source code > attachment is correct. The only downside is a bigger JAR, which in my > view is a low price to pay for enhanced productivity and troubleshooting > reliability. To put the "bigger JAR" issue into context: > > 444463 2006-06-17 03:50 acegi-security-1.0.1.jar > 529413 2006-06-23 05:34 acegi-security-1.0.1-sources.jar > > Based on release 1.0.1, we'd go from a 444Kb release to a 973Kb combined > JAR. I don't think this is a serious issue from a download or disk space > perspective. Especially concerned people can always re-jar for their > production deployment. > > How would people feel about future Acegi Security release JARs including > source code, as per GWT? I guess we could continue to have two releases, > but our acegi-security-<release>-sources.jar would contain *both* > classes and source code. > > It would be good to discuss this and get some feedback from the community. > > Cheers > Ben > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Home: http://acegisecurity.org > Acegisecurity-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
