Re: archiva-1.0.2 eta?
Did you switch to a build of 1.0.2-SNAPSHOT which caused the issue to not become reproducible, or have you stopped observing it in your current installation? Thanks, Brett On 24/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: In particular, I would like the fixes for the following issues: * http://jira.codehaus.org/browse/MRM-674 * http://jira.codehaus.org/browse/MRM-632 * http://jira.codehaus.org/browse/MRM-691 Only the last one still needs to be fixed, if it is still an issue. I am not able to reproduce it anymore. -Original Message- From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are there any specific bugs in the bug tracking system that you feel need attention? Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi Archiva overall open (non-future) bugs - http://urltea.com/2rqj - Joakim Jason Chaffee wrote: Is there an ETA on the 1.0.2 release? I would really like to get a couple of bug fixes. -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: Archiva crashes after a couple of days
On 23/02/2008, Eric Miles [EMAIL PROTECTED] wrote: Wow, you got us beat. Those are pretty large repos. Maybe the Archiva team can comment on this. I'm interested to hear what they say. I run it on localhost with just around 500M which is all the stuff from central that I use on a daily basis. We've successfully run it on a copy of the central repository which I believe has a similar number of artifacts but is not as large. I have also run it on an 80G repo that was mostly very large files, so a smaller number of artifacts. We have got some reports of excessive memory use (which might cause this) over a large number of proxy requests and James has been investigating that recently. I think we can certainly resolve this problem with more investigation if it continues - but it really needs some more information on what is happening in that environment and narrowing down the possible causes. Cheers, Brett -- Brett Porter Blog: http://blogs.exist.com/bporter/
RE: archiva-1.0.2 eta?
Actually, I misspoke. I checked the logs again today and saw the NPE during the database scanning. I am not sure what is going on because I didn't change any of the database configuration from installed defaults. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 12:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Did you switch to a build of 1.0.2-SNAPSHOT which caused the issue to not become reproducible, or have you stopped observing it in your current installation? Thanks, Brett On 24/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote: In particular, I would like the fixes for the following issues: * http://jira.codehaus.org/browse/MRM-674 * http://jira.codehaus.org/browse/MRM-632 * http://jira.codehaus.org/browse/MRM-691 Only the last one still needs to be fixed, if it is still an issue. I am not able to reproduce it anymore. -Original Message- From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] Sent: Friday, February 22, 2008 5:31 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are there any specific bugs in the bug tracking system that you feel need attention? Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi Archiva overall open (non-future) bugs - http://urltea.com/2rqj - Joakim Jason Chaffee wrote: Is there an ETA on the 1.0.2 release? I would really like to get a couple of bug fixes. -- Brett Porter Blog: http://blogs.exist.com/bporter/
Re: How can I get all the jars I need from repository?
On Sat, 2008-02-23 at 23:08 -0800, youhaodeyi wrote: Maven downloads some jars my java application uses to the repository. The repository also includes many jars that my application doesn't need. When I release my software, how can I get the jars I need from the repository? Do you mean that you want to create a zip-file containing your code plus all of the libraries it depends on? Have a look at the documentation for the maven-assembly-plugin and the maven-dependency-plugin. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is there two configuration files for Maven, settings.xml and pom.xml
On Sat, 2008-02-23 at 23:53 -0800, youhaodeyi wrote: Can I put the configurations in settings.xml to pom.xml? Why does maven use two configuration files? The pom.xml is meant to be checked in to your version control system, and will be published to the maven repository. This should produce a normal build without any external settings. The settings.xml file can do per-person overrides of stuff in the pom.xml. Of course this is not normally checked in, and is never available in the maven repository. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
manifest problem Please help
Hi All
I'm using maven -2.0.7 and have jar configuration has follows
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
version2.2/version
configuration
archive
manifestFile${basedir}/ejbModule/META-INF/MANIFEST.MF/manifestFile
/archive
/configuration
/plugin
and my MANIFEST.MF @ ejbModule/META-INF/MANIFEST.MF has some custom entry,
but this file never makes into jar file, i've only the regular maven created
MANIFEST.MF only.
i also tried to with manifestEntries, addClasspath nothing worked for
me.
I'm sure i'm doing something wrong, can anyone please give some working
sample for these option
Your help is very much appreciated
Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM
As for the comparison between maven integration solutions, I know none but it would be interesting if someone started one (like a google group and some pages on it). Since I'm involved with q4e, it would not be a fair comparison if I made it :-). I think it would be easy to have a feature matrix just if several users of the different solutions exchanged opinions on a list. As for cleaning the project from the shell... if you use eclipse, you'll need to refresh/rebuild the workspace. This is not a problem with the plug-ins, but something that goes deep in the eclipse architecture. Rodrigo Madera wrote: Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project? I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee [EMAIL PROTECTED] wrote: I found the following FAQ about Q4E: http://code.google.com/p/q4e/wiki/FAQ Features * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * keeping Eclipse classpath synchronized with Maven POM * dependency graphing http://code.google.com/p/q4e/wiki/DependencyGraphViewer * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects * ability to import parent projects (pom projects) http://code.google.com/p/q4e/wiki/ImportingMultiprojects (from 0.5.0) * ability to cancel maven builds (from 0.5.0) * dependency analysis tooling (from 0.5.0) What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation http://www.eclipse.org , for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz http://www.devzuz.com , an Eclipse Strategic Developer Member http://www.eclipse.org/membership/showMember.php?member_id=824 we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, or creation of new projects using the archetype mechanism are only present in Q. Also it's implemented in several modules with reusability and extension in mind so other people can develop their own plugins taking advantage of the functionality they need (see for instance Candy for Appfuse http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be -under-extreme-refactoring/http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/ ). In any case the underlying Maven libraries used for both plugins are the same (the Maven Embedder) and both plugin developers collaborate in its development. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, February 23, 2008 5:45 PM To: users@maven.apache.org Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM I googled around to try to find a comparison between Mevenide and the alternatives, and didn't come up with much. Can someone tell me the differences? (I've spend some time with m2eclipse, and I'm *not* impressed). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - http://www.linkedin.com/in/amuino Abel Muintilde;o Vizcaino - http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com -- View this message in context: http://www.nabble.com/Mevenide-vs.-M2Eclipse%2C-Q-for-Eclipse-IAM-tp15659809s177p15662411.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manifest problem Please help
If this is EJB jar to build, then you should configure ejb-plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
archive
manifestFile${basedir}/ejbModule/META-INF/MANIFEST.MF/manifestFile
/archive
- markku
I am Who i am wrote:
Hi All
I'm using maven -2.0.7 and have jar configuration has follows
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
version2.2/version
configuration
archive
manifestFile${basedir}/ejbModule/META-INF/MANIFEST.MF/manifestFile
/archive
/configuration
/plugin
and my MANIFEST.MF @ ejbModule/META-INF/MANIFEST.MF has some custom entry,
but this file never makes into jar file, i've only the regular maven created
MANIFEST.MF only.
i also tried to with manifestEntries, addClasspath nothing worked for
me.
I'm sure i'm doing something wrong, can anyone please give some working
sample for these option
Your help is very much appreciated
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: manifest problem Please help
I already tried all of them, no use
On 2/24/08, Dennis Lundberg [EMAIL PROTECTED] wrote:
Did you try following the documentation to the letter:
http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
http://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html
http://maven.apache.org/shared/maven-archiver/examples/classpath.html
I am Who i am wrote:
Hi All
I'm using maven -2.0.7 and have jar configuration has follows
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
version2.2/version
configuration
archive
manifestFile${basedir}/ejbModule/META-INF/MANIFEST.MF/manifestFile
/archive
/configuration
/plugin
and my MANIFEST.MF @ ejbModule/META-INF/MANIFEST.MF has some custom
entry,
but this file never makes into jar file, i've only the regular maven
created
MANIFEST.MF only.
i also tried to with manifestEntries, addClasspath nothing worked
for
me.
I'm sure i'm doing something wrong, can anyone please give some working
sample for these option
Your help is very much appreciated
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: manifest problem Please help
Have a look at useDefaultManifestFile mojo parameter [1]
It's false by default to preserve backward compatibility (look MJAR-71
[2] for details).
--
Olivier
[1]
http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html#useDefaultManifestFile
[2] http://jira.codehaus.org/browse/MJAR-71
2008/2/24, I am Who i am [EMAIL PROTECTED]:
I already tried all of them, no use
On 2/24/08, Dennis Lundberg [EMAIL PROTECTED] wrote:
Did you try following the documentation to the letter:
http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
http://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html
http://maven.apache.org/shared/maven-archiver/examples/classpath.html
I am Who i am wrote:
Hi All
I'm using maven -2.0.7 and have jar configuration has follows
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
version2.2/version
configuration
archive
manifestFile${basedir}/ejbModule/META-INF/MANIFEST.MF/manifestFile
/archive
/configuration
/plugin
and my MANIFEST.MF @ ejbModule/META-INF/MANIFEST.MF has some custom
entry,
but this file never makes into jar file, i've only the regular maven
created
MANIFEST.MF only.
i also tried to with manifestEntries, addClasspath nothing worked
for
me.
I'm sure i'm doing something wrong, can anyone please give some working
sample for these option
Your help is very much appreciated
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Setting up relative testpaths
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I got a test that needs to read a file in src/test/resources. How should I write the test to get the information about the relative path to that file, either using TestNG or just plain Junit? Kind regards, Tarjei -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHwXSZYVRKCnSvzfIRApi3AJ9BqL+U4acMHTDeOjwnqP9/jru/OQCfYXqJ hE4f1vgaeBVWkww/ngZ5KFM= =kkm7 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up relative testpaths
On Sun, 2008-02-24 at 14:43 +0100, tarjei wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I got a test that needs to read a file in src/test/resources. How should I write the test to get the information about the relative path to that file, either using TestNG or just plain Junit? It's best to avoid files at all. Where possible, I suggest using Class.getResourceAsStream(...) to access the data you want. The stuff in src/test/resources is on the classpath. If you really need a File object, then try URL url = Class.getResource(...); File f = url.tgetFile() Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up relative testpaths
tarjei wrote: Hi, I got a test that needs to read a file in src/test/resources. How should I write the test to get the information about the relative path to that file, either using TestNG or just plain Junit? I got unpredictable results when using test-resources and maven: eclipse (junit plugin) and mvn test both ran successfully the test but mvn install or mvn tomcat:deploy failed. Avoid test-resources if possible. Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up relative testpaths
On Sun, 2008-02-24 at 16:09 +0100, Jan Torben Heuer wrote: tarjei wrote: Hi, I got a test that needs to read a file in src/test/resources. How should I write the test to get the information about the relative path to that file, either using TestNG or just plain Junit? I got unpredictable results when using test-resources and maven: eclipse (junit plugin) and mvn test both ran successfully the test but mvn install or mvn tomcat:deploy failed. Avoid test-resources if possible. Well, I use it extensively in half-a-dozen different projects and have no such problems... Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ANN Maven Archetype Plugin 2.0-alpha-2
The Maven team would like to announce the release of Maven Archetype 2.0-alpha-2. This release corrected backwards compatibility with the 1.0 version and a few windows issues. The site has also been updated and deployed: http://maven.apache.org/plugins/maven-archetype-plugin Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Use the -U flag to get the updated plugin. Enjoy. -- The Maven Team. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up relative testpaths
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 simon wrote: On Sun, 2008-02-24 at 14:43 +0100, tarjei wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I got a test that needs to read a file in src/test/resources. How should I write the test to get the information about the relative path to that file, either using TestNG or just plain Junit? It's best to avoid files at all. Where possible, I suggest using Class.getResourceAsStream(...) to access the data you want. The stuff in src/test/resources is on the classpath. If you really need a File object, then try URL url = Class.getResource(...); File f = url.tgetFile() Thanks, that nailed it. Tarjei Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHwZPkYVRKCnSvzfIRAnGUAKCvNN6olUYXmpnkN8ijPjMO29cT/gCcDDkr vxApKdlxKGixGolmnGYTC60= =SNoo -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JNI, freehep-nar-plugin and assembly plugin question
You can use the dependency plugin to unpack your zip. It's not clear though if you are trying to include the .so's into the NAR or something else. If it's something else, you can use the assembly plugin to pick up what you need. If it's the nar, then you'll have to experiment with where to unpack the files so they get included. -Original Message- From: Eugeny N Dzhurinsky [mailto:[EMAIL PROTECTED] Sent: Saturday, February 23, 2008 10:56 AM To: users@maven.apache.org Subject: JNI, freehep-nar-plugin and assembly plugin question Hello, everybody! I need some help with this task: We have a project which consists of several modules, and now we need to add the new one - but this module has a binding to JNI, which requires to compile and link native code. After the research I've found there is a plugin at FreeHEP (freehep-nar-plugin) which seems to perform such kind of task and is able to compile and link native sources within Maven. This works fine until we tried to assemble the application in single ZIP archive - we need to include the *.so files in this archive, however the nar plugin does create a some archive (*.nar) which includes these SO files, and the question now - how is it possible to unpack this archive (looks like it is a regular ZIP file?) BEFORE assembling and then include the *.so files into resulting archive. Thank you in advance! -- Eugene N Dzhurinsky - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JNI, freehep-nar-plugin and assembly plugin question
Could you provide specifics on where to obtain maven-assembly-plugin? I did'nt see any information in maven distro on NAR...could you provide any relevant information on use and configuration? Thanks Martin-- - Original Message - From: Brian E. Fox [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Sunday, February 24, 2008 11:09 AM Subject: RE: JNI, freehep-nar-plugin and assembly plugin question You can use the dependency plugin to unpack your zip. It's not clear though if you are trying to include the .so's into the NAR or something else. If it's something else, you can use the assembly plugin to pick up what you need. If it's the nar, then you'll have to experiment with where to unpack the files so they get included. -Original Message- From: Eugeny N Dzhurinsky [mailto:[EMAIL PROTECTED] Sent: Saturday, February 23, 2008 10:56 AM To: users@maven.apache.org Subject: JNI, freehep-nar-plugin and assembly plugin question Hello, everybody! I need some help with this task: We have a project which consists of several modules, and now we need to add the new one - but this module has a binding to JNI, which requires to compile and link native code. After the research I've found there is a plugin at FreeHEP (freehep-nar-plugin) which seems to perform such kind of task and is able to compile and link native sources within Maven. This works fine until we tried to assemble the application in single ZIP archive - we need to include the *.so files in this archive, however the nar plugin does create a some archive (*.nar) which includes these SO files, and the question now - how is it possible to unpack this archive (looks like it is a regular ZIP file?) BEFORE assembling and then include the *.so files into resulting archive. Thank you in advance! -- Eugene N Dzhurinsky - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ANN Maven Archetype Plugin 2.0-alpha-2
Much appreciated backwards compat. Thanks!! Rodrigo On Sat, Feb 23, 2008 at 12:20 AM, Brian Fox [EMAIL PROTECTED] wrote: The Maven team would like to announce the release of Maven Archetype 2.0-alpha-2. This release corrected backwards compatibility with the 1.0 version and a few windows issues. The site has also been updated and deployed: http://maven.apache.org/plugins/maven-archetype-plugin Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Use the -U flag to get the updated plugin. Enjoy. -- The Maven Team. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Fwd: OutOfMemoryError during plugin execution, yet build continues!]
Has anyone encountered anything like this before? What is the fix? Sahoo ---BeginMessage--- I am seeing something very strange. We have our own plugin(it's basically an annotation processor) that gets invoked as part of compile phase. It appears that the JVM gets OutOfMemoryError when this plugin is executed, yet the build continues to the next phase instead of aborting. I ran with -X option and it shows that the plugin is invoked in process. I have looked at our plugin code and we do not catch Throwable or Error in our code. So, it appears to be a bug in Maven. Given below is some selected output that I think should give an idea of what's going on... [INFO] [INFO] Building Web Container for GlassFish [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. ... [DEBUG] Configuring mojo 'com.sun.enterprise:hk2-maven-plugin:0.2-SNAPSHOT:hk2-compile' -- ... [DEBUG] (f) fork = false ... [INFO] [hk2:hk2-compile] [DEBUG] Using compiler 'hk2-apt'. [DEBUG] Source directories: [/space/ss141213/WS/gf/v3/web/webtier/src/main/java] [DEBUG] Classpath: [/space/ss141213/WS/gf/v3/web/webtier/target/classes... [INFO] Compiling 660 source files to /space/ss141213/WS/gf/v3/web/webtier/target/classes The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:99) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:393) at java.lang.StringBuilder.append(StringBuilder.java:120) at com.sun.tools.javac.jvm.ClassReader.list(ClassReader.java:1756) at com.sun.tools.javac.jvm.ClassReader.listAll(ClassReader.java:1882) at com.sun.tools.javac.jvm.ClassReader.fillIn(ClassReader.java:1901) at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1538) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) at com.sun.tools.javac.jvm.ClassReader.completeOwners(ClassReader.java:1547) at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1534) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:612) at com.sun.tools.javac.code.Symbol$ClassSymbol.flags(Symbol.java:550) at com.sun.tools.javac.code.Types$AsSuperFcn.visitClassType(Types.java:1440) at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:482) at com.sun.tools.javac.code.Types$AsSuperFcn.asSuper(Types.java:1417) at com.sun.tools.javac.code.Types$AsSuperFcn.visitClassType(Types.java:1434) at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:482) at com.sun.tools.javac.code.Types$AsSuperFcn.asSuper(Types.java:1417) at com.sun.tools.javac.code.Types.asSuper(Types.java:1407) at com.sun.tools.javac.code.Types$IsSubTypeFcn.visitClassType(Types.java:429) at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:482) at com.sun.tools.javac.code.Types$IsSubTypeFcn.isSubType(Types.java:353) at com.sun.tools.javac.code.Types.isSubType(Types.java:331) at com.sun.tools.javac.code.Types.isSubTypeUnchecked(Types.java:311) at com.sun.tools.javac.code.Types.isConvertible(Types.java:278) at com.sun.tools.javac.code.Types.isAssignable(Types.java:1630) at com.sun.tools.javac.comp.Check.checkType(Check.java:325) at com.sun.tools.javac.comp.Annotate.enterAnnotation(Annotate.java:122) at com.sun.tools.javac.comp.MemberEnter.enterAnnotations(MemberEnter.java:705) Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. ... Thanks, Sahoo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---End Message--- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM
Since the question of choosing an Eclipse Integration is often asked, I just worked on the Eclipse Integration page from Maven Users Wiki: http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration I started a comparison matrix with basic project informations. This Wiki is public: feel free to improve the comparison. Selon Abel Muiño [EMAIL PROTECTED]: As for the comparison between maven integration solutions, I know none but it would be interesting if someone started one (like a google group and some pages on it). Since I'm involved with q4e, it would not be a fair comparison if I made it :-). I think it would be easy to have a feature matrix just if several users of the different solutions exchanged opinions on a list. As for cleaning the project from the shell... if you use eclipse, you'll need to refresh/rebuild the workspace. This is not a problem with the plug-ins, but something that goes deep in the eclipse architecture. Rodrigo Madera wrote: Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project? I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee [EMAIL PROTECTED] wrote: I found the following FAQ about Q4E: http://code.google.com/p/q4e/wiki/FAQ Features * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * keeping Eclipse classpath synchronized with Maven POM * dependency graphing http://code.google.com/p/q4e/wiki/DependencyGraphViewer * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects * ability to import parent projects (pom projects) http://code.google.com/p/q4e/wiki/ImportingMultiprojects (from 0.5.0) * ability to cancel maven builds (from 0.5.0) * dependency analysis tooling (from 0.5.0) What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation http://www.eclipse.org , for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz http://www.devzuz.com , an Eclipse Strategic Developer Member http://www.eclipse.org/membership/showMember.php?member_id=824 we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, or creation of new projects using the archetype mechanism are only present in Q. Also it's implemented in several modules with reusability and extension in mind so other people can develop their own plugins taking advantage of the functionality they need (see for instance Candy for Appfuse http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be -under-extreme-refactoring/http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/ ). In any case the underlying Maven libraries used for both plugins are the same (the Maven Embedder) and both plugin developers collaborate in its development. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, February 23, 2008 5:45 PM To: users@maven.apache.org Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM I googled around to try to find a comparison between Mevenide and the alternatives, and didn't come up with much. Can someone tell me the differences? (I've spend some time with m2eclipse, and I'm *not* impressed). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - http://www.linkedin.com/in/amuino Abel Muintilde;o Vizcaino - http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com -- View this message in context: http://www.nabble.com/Mevenide-vs.-M2Eclipse%2C-Q-for-Eclipse-IAM-tp15659809s177p15662411.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM
Nice work. However there is a deprecated indicator on the OSGi Bundles item (under Eclipse Developer). What exactly do you mean with it? As an OSGi developer I found it rather strange to see OSGi and deprecated on the same sentence. =o) Thanks, Rodrigo On Sun, Feb 24, 2008 at 6:04 PM, [EMAIL PROTECTED] wrote: Since the question of choosing an Eclipse Integration is often asked, I just worked on the Eclipse Integration page from Maven Users Wiki: http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration I started a comparison matrix with basic project informations. This Wiki is public: feel free to improve the comparison. Selon Abel Muiño [EMAIL PROTECTED]: As for the comparison between maven integration solutions, I know none but it would be interesting if someone started one (like a google group and some pages on it). Since I'm involved with q4e, it would not be a fair comparison if I made it :-). I think it would be easy to have a feature matrix just if several users of the different solutions exchanged opinions on a list. As for cleaning the project from the shell... if you use eclipse, you'll need to refresh/rebuild the workspace. This is not a problem with the plug-ins, but something that goes deep in the eclipse architecture. Rodrigo Madera wrote: Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project? I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee [EMAIL PROTECTED] wrote: I found the following FAQ about Q4E: http://code.google.com/p/q4e/wiki/FAQ Features * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * keeping Eclipse classpath synchronized with Maven POM * dependency graphing http://code.google.com/p/q4e/wiki/DependencyGraphViewer * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects * ability to import parent projects (pom projects) http://code.google.com/p/q4e/wiki/ImportingMultiprojects (from 0.5.0) * ability to cancel maven builds (from 0.5.0) * dependency analysis tooling (from 0.5.0) What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation http://www.eclipse.org , for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz http://www.devzuz.com , an Eclipse Strategic Developer Member http://www.eclipse.org/membership/showMember.php?member_id=824 we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, or creation of new projects using the archetype mechanism are only present in Q. Also it's implemented in several modules with reusability and extension in mind so other people can develop their own plugins taking advantage of the functionality they need (see for instance Candy for Appfuse http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be -under-extreme-refactoring/ http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/ ). In any case the underlying Maven libraries used for both plugins are the same (the Maven Embedder) and both plugin developers collaborate in its development. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, February 23, 2008 5:45 PM To: users@maven.apache.org Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM I googled around to try to find a comparison between Mevenide and the alternatives, and didn't come up with much. Can someone tell me the differences? (I've spend some time with m2eclipse, and I'm *not* impressed). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - http://www.linkedin.com/in/amuino Abel Muintilde;o Vizcaino - http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com -- View this message in context:
Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM
Selon Rodrigo Madera [EMAIL PROTECTED]: Nice work. thank you However there is a deprecated indicator on the OSGi Bundles item (under Eclipse Developer). What exactly do you mean with it? *I* don't mean anything: it was in the page before I changed it. Since I don't know the topic, I let it as-is. Feel free to fix the info if it is not accurate :) As an OSGi developer I found it rather strange to see OSGi and deprecated on the same sentence. =o) Thanks, Rodrigo On Sun, Feb 24, 2008 at 6:04 PM, [EMAIL PROTECTED] wrote: Since the question of choosing an Eclipse Integration is often asked, I just worked on the Eclipse Integration page from Maven Users Wiki: http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration I started a comparison matrix with basic project informations. This Wiki is public: feel free to improve the comparison. Selon Abel Muiño [EMAIL PROTECTED]: As for the comparison between maven integration solutions, I know none but it would be interesting if someone started one (like a google group and some pages on it). Since I'm involved with q4e, it would not be a fair comparison if I made it :-). I think it would be easy to have a feature matrix just if several users of the different solutions exchanged opinions on a list. As for cleaning the project from the shell... if you use eclipse, you'll need to refresh/rebuild the workspace. This is not a problem with the plug-ins, but something that goes deep in the eclipse architecture. Rodrigo Madera wrote: Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project? I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee [EMAIL PROTECTED] wrote: I found the following FAQ about Q4E: http://code.google.com/p/q4e/wiki/FAQ Features * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * keeping Eclipse classpath synchronized with Maven POM * dependency graphing http://code.google.com/p/q4e/wiki/DependencyGraphViewer * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects * ability to import parent projects (pom projects) http://code.google.com/p/q4e/wiki/ImportingMultiprojects (from 0.5.0) * ability to cancel maven builds (from 0.5.0) * dependency analysis tooling (from 0.5.0) What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation http://www.eclipse.org , for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz http://www.devzuz.com , an Eclipse Strategic Developer Member http://www.eclipse.org/membership/showMember.php?member_id=824 we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, or creation of new projects using the archetype mechanism are only present in Q. Also it's implemented in several modules with reusability and extension in mind so other people can develop their own plugins taking advantage of the functionality they need (see for instance Candy for Appfuse http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be -under-extreme-refactoring/ http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/ ). In any case the underlying Maven libraries used for both plugins are the same (the Maven Embedder) and both plugin developers collaborate in its development. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, February 23, 2008 5:45 PM To: users@maven.apache.org Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM I googled around to try to find a comparison between Mevenide and the alternatives, and didn't come up with much. Can someone tell me the differences? (I've spend some time with m2eclipse, and I'm *not* impressed).
Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM
i've added a list of Q4E features to the table On Sun, Feb 24, 2008 at 10:04 AM, [EMAIL PROTECTED] wrote: Since the question of choosing an Eclipse Integration is often asked, I just worked on the Eclipse Integration page from Maven Users Wiki: http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration I started a comparison matrix with basic project informations. This Wiki is public: feel free to improve the comparison. Selon Abel Muiño [EMAIL PROTECTED]: As for the comparison between maven integration solutions, I know none but it would be interesting if someone started one (like a google group and some pages on it). Since I'm involved with q4e, it would not be a fair comparison if I made it :-). I think it would be easy to have a feature matrix just if several users of the different solutions exchanged opinions on a list. As for cleaning the project from the shell... if you use eclipse, you'll need to refresh/rebuild the workspace. This is not a problem with the plug-ins, but something that goes deep in the eclipse architecture. Rodrigo Madera wrote: Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project? I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee [EMAIL PROTECTED] wrote: I found the following FAQ about Q4E: http://code.google.com/p/q4e/wiki/FAQ Features * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * keeping Eclipse classpath synchronized with Maven POM * dependency graphing http://code.google.com/p/q4e/wiki/DependencyGraphViewer * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects * ability to import parent projects (pom projects) http://code.google.com/p/q4e/wiki/ImportingMultiprojects (from 0.5.0) * ability to cancel maven builds (from 0.5.0) * dependency analysis tooling (from 0.5.0) What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation http://www.eclipse.org , for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz http://www.devzuz.com , an Eclipse Strategic Developer Member http://www.eclipse.org/membership/showMember.php?member_id=824 we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, or creation of new projects using the archetype mechanism are only present in Q. Also it's implemented in several modules with reusability and extension in mind so other people can develop their own plugins taking advantage of the functionality they need (see for instance Candy for Appfuse http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be -under-extreme-refactoring/http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/ ). In any case the underlying Maven libraries used for both plugins are the same (the Maven Embedder) and both plugin developers collaborate in its development. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, February 23, 2008 5:45 PM To: users@maven.apache.org Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM I googled around to try to find a comparison between Mevenide and the alternatives, and didn't come up with much. Can someone tell me the differences? (I've spend some time with m2eclipse, and I'm *not* impressed). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - http://www.linkedin.com/in/amuino Abel Muintilde;o Vizcaino - http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com -- View this message in context: http://www.nabble.com/Mevenide-vs.-M2Eclipse%2C-Q-for-Eclipse-IAM-tp15659809s177p15662411.html Sent from the Maven - Users mailing
Packaging plugin docs (was: manifest problem Please help)
Hi Dennis, Your email below was exactly what I needed. It also makes me ask this question how do users know to look at the archiver plugin options for the packaging-type plugins?. E.g. my recent escapade into making a war (converting an M1 build to M2) - I was in the middle of trying to determine how to use an existing manifest file vs having Maven generate one when I read your below email. There are a number of nice examples of manifest file manipulation in the war plugin docs, but nothing on using a file. Same is true for the Guide to Working with Manifests page. So I visited the archiver docs, and there was my answer! Nothing I found on the war plugin's docs leads the user to look at the archiver info (and with a quick glance at the EAR one I did not see anything on other packaging plugins; my guess is I will have similar questions on the EAR plugin). Assuming all of these packaging plugins use archiver (could be a wrong assumption!), I am thinking we should add to each of the packaging plugins a simple sentence or two stating to also refer to the Archiver docs for further configuration examples and a link to it. Otherwise, it takes preexisting knowledge to know to look there. WDYT? Additionally, the archiver plugin is not listed on the http://maven.apache.org/plugins/ page. This also leads me to wonder if different doc page(s) exist for a plugin list. I think probably not, and this is just a doc maintenance issue, which hints to auto-generating a plugin list page with description and link to its page. That's a different issue of course! :-) generalThoughtBesides these specifics on archiver, the configuration element options per plugin seem a little bit elusive - we rely on examples on the plugin doc page, which I think the existing ones are good, just incomplete at times [cite above case]. Not knowing what would be the answer other than something like the M1 properties list pages (properties could still get overlooked, of course). One thing I miss with the configuration elements that we have with most of the POM is what XML schema provides for IDE smart completion./generalThought -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 4:44 AM To: Maven Users List Subject: Re: manifest problem Please help Did you try following the documentation to the letter: http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html http://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html http://maven.apache.org/shared/maven-archiver/examples/classpath.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM
How about mevenide? Has anyone used it, know how it compares? Carlos Sanchez wrote: i've added a list of Q4E features to the table On Sun, Feb 24, 2008 at 10:04 AM, [EMAIL PROTECTED] wrote: Since the question of choosing an Eclipse Integration is often asked, I just worked on the Eclipse Integration page from Maven Users Wiki: http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration I started a comparison matrix with basic project informations. This Wiki is public: feel free to improve the comparison. Selon Abel Muiño [EMAIL PROTECTED]: As for the comparison between maven integration solutions, I know none but it would be interesting if someone started one (like a google group and some pages on it). Since I'm involved with q4e, it would not be a fair comparison if I made it :-). I think it would be easy to have a feature matrix just if several users of the different solutions exchanged opinions on a list. As for cleaning the project from the shell... if you use eclipse, you'll need to refresh/rebuild the workspace. This is not a problem with the plug-ins, but something that goes deep in the eclipse architecture. Rodrigo Madera wrote: Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project? I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee [EMAIL PROTECTED] wrote: I found the following FAQ about Q4E: http://code.google.com/p/q4e/wiki/FAQ Features * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * keeping Eclipse classpath synchronized with Maven POM * dependency graphing http://code.google.com/p/q4e/wiki/DependencyGraphViewer * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects * ability to import parent projects (pom projects) http://code.google.com/p/q4e/wiki/ImportingMultiprojects (from 0.5.0) * ability to cancel maven builds (from 0.5.0) * dependency analysis tooling (from 0.5.0) What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation http://www.eclipse.org , for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz http://www.devzuz.com , an Eclipse Strategic Developer Member http://www.eclipse.org/membership/showMember.php?member_id=824 we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, or creation of new projects using the archetype mechanism are only present in Q. Also it's implemented in several modules with reusability and extension in mind so other people can develop their own plugins taking advantage of the functionality they need (see for instance Candy for Appfuse http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be -under-extreme-refactoring/http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/ ). In any case the underlying Maven libraries used for both plugins are the same (the Maven Embedder) and both plugin developers collaborate in its development. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, February 23, 2008 5:45 PM To: users@maven.apache.org Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM I googled around to try to find a comparison between Mevenide and the alternatives, and didn't come up with much. Can someone tell me the differences? (I've spend some time with m2eclipse, and I'm *not* impressed). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - http://www.linkedin.com/in/amuino Abel Muintilde;o Vizcaino - http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com -- View this message in context: http://www.nabble.com/Mevenide-vs.-M2Eclipse%2C-Q-for-Eclipse-IAM-tp15659809s177p15662411.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Packaging plugin docs
Jeff Jensen wrote: Hi Dennis, Your email below was exactly what I needed. It also makes me ask this question how do users know to look at the archiver plugin options for the packaging-type plugins?. E.g. my recent escapade into making a war (converting an M1 build to M2) - I was in the middle of trying to determine how to use an existing manifest file vs having Maven generate one when I read your below email. There are a number of nice examples of manifest file manipulation in the war plugin docs, but nothing on using a file. Same is true for the Guide to Working with Manifests page. So I visited the archiver docs, and there was my answer! Nothing I found on the war plugin's docs leads the user to look at the archiver info (and with a quick glance at the EAR one I did not see anything on other packaging plugins; my guess is I will have similar questions on the EAR plugin). This is a maintenance issue. The site for the archiver was created in the process of releasing maven-jar-plugin 2.2. We took the best docs we could find on the subject and put it in a single place (archiver). The site for the jar plugin was updated accordingly, referring to the archiver docs when appropriate. Any duplicate docs was removed from the jar plugin site. Assuming all of these packaging plugins use archiver (could be a wrong assumption!), I am thinking we should add to each of the packaging plugins a simple sentence or two stating to also refer to the Archiver docs for further configuration examples and a link to it. Otherwise, it takes preexisting knowledge to know to look there. WDYT? The other archive-ish plugins (war and ear) should get the same treatment for their respective next release. Additionally, the archiver plugin is not listed on the http://maven.apache.org/plugins/ page. This also leads me to wonder if different doc page(s) exist for a plugin list. I think probably not, and this is just a doc maintenance issue, which hints to auto-generating a plugin list page with description and link to its page. That's a different issue of course! :-) The archiver isn't a plugin in itself, but something we call a shared component. There are other shared components as well, but they are somewhat lacking in the documentation area. But creating a starting page for them, similar to the plugins page, is a good idea. generalThoughtBesides these specifics on archiver, the configuration element options per plugin seem a little bit elusive - we rely on examples on the plugin doc page, which I think the existing ones are good, just incomplete at times [cite above case]. Not knowing what would be the answer other than something like the M1 properties list pages (properties could still get overlooked, of course). There is an auto-generated page for every plugin, describing the configuration elements for each goal. Click the Goals link in the menu and then on a specific goal. The page relies on annotations in the Javadoc of the plugin. One thing I miss with the configuration elements that we have with most of the POM is what XML schema provides for IDE smart completion./generalThought -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 4:44 AM To: Maven Users List Subject: Re: manifest problem Please help Did you try following the documentation to the letter: http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html http://maven.apache.org/shared/maven-archiver/examples/manifestEntries.html http://maven.apache.org/shared/maven-archiver/examples/classpath.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly plugin and project inheritance
Copy requires that the artifact must be in the local repository or in a
remote repository.
The copy dependencies allows for the artifact to come from the reactor, so
you don't have to install the artifact into your local repository.
The copy dependencies can be set to only copy one dependency.
Trust me, this is the better way to do it.
-Stephen
On Sat, Feb 23, 2008 at 9:38 PM, Reto Bachmann-Gmür [EMAIL PROTECTED] wrote:
Thank you very much for your help, I can now have many projects generate
the right assembly with just one assembly descriptor and without
requiring to check out multiple projects (and having them at the right
position in the directory structure).
I don't understand your suggestion to use copy-dependencies, what I'm
doing is copying a single resource (the assembly descriptor) and not all
of the dependencies. The copy goal seems to do its job.
Cheers,
reto
Stephen Connolly wrote:
there are two sets of goals in the maven dependency plugin.
the first set are copy and unpack. you specify the artifacts inside
the plugin configuration. these are not the set you want. the set you
want are copy-dependencies (or something like that I am on my iPod so
you will have to check) with this set you add the dependency to the
pom. that will force maven to sequence things correctly for you.
the build helper plugin has a default phase, so leave that alone. I
would bind the dependency plugin to one of the generate phases
(sources or resources)
Stephen
2/22/08, Reto Bachmann-Gmür [EMAIL PROTECTED] wrote:
The version I posted doesn't work as the child-projects can't perform
the attach-artifact attached to the package phase.
I've now extracted the dist configuration and the attachment of it to a
separate project[1]. Having done this I also attached the copy and the
assembly goals to the compile and package phases [2].
1.
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps-assembly/trunk/pom.xml
2. in
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/pom.xml
Reto Bachmann-Gmür wrote:
Thanks Stephen,
trying to follow the path you describe I added the following to the
parent-pom:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuild-helper-maven-plugin/artifactId
executions
execution
idattach-artifacts/id
phasepackage/phase
goals
goalattach-artifact/goal
/goals
configuration
artifacts
artifact
filesrc/assembly/dist.xml/file
typexml/type
classifier
assembly-descriptor
/classifier
/artifact
/artifacts
/configuration
/execution
/executions
/plugin
and
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
artifactItems
artifactItem
groupIdorg.wymiwyg.rwcf/groupId
artifactIdrwcf-apps/artifactId
version0.0.1/version
typexml/type
classifierassembly-descriptor/classifier
overWritefalse/overWrite
outputDirectory
${project.build.directory}/src/assembly/
/outputDirectory
destFileNamedist.xml/destFileName
/artifactItem
/artifactItems
/configuration
/plugin
furthermore I changed the descriptor of maven-assembly-plugin to use
${project.build.directory}/src/assembly/dist.xml. I didn't change
anything to the child-projects.
I can now execute mvn clean dependency:copy assembly:assembly for
child projects to create a distribution-package.
The only thing which I'm still insecure is about attaching this to
phases, the difficulty seems that the super project doesn't need to
have this attached to any phase, and the dependency resolution fails
unless executed after install (a solution might be to split the parent
into a grand-parent providing the assembly descriptor and binding it
to phases in the intermediate parent). But I'm not sure anyway in
which phase to best create zip and tar.
Cheers,
reto
Stephen Connolly wrote:
You could attach the common descriptor as a build artifact one
module, and
then use the dependency plugin to pull it down to each child module.
i.e.
Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a
classifier of, e.g. assembly-descriptor.
Now when you run mvn install or mvn deploy on rwcf-apps the
descriptor will
be published to the maven repository (local or remote respectively)
Then in one of the modules that you want to use this common
descriptor, add
a dependency on the rwcf-apps with a type of assembly-descriptor, you
use
maven-dependency-plugin to copy the dependency to your target
directory, and
then your pom just directs the assembly plugin to use that
descriptor.
-Stephen
On Thu, Feb 21, 2008 at 8:47 PM, Reto Bachmann-Gmür [EMAIL PROTECTED]
wrote:
Hello
I'm having many projects that share some dependencies and that
should be
packaged the same way. So I wanted to have a parent project
configuring
the maven-assembly-plugin.
I
Re: assembly plugin and project inheritance
If you do something like
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
*includeTypesassembly-descriptor**includeTypes*
...**
/configuration
goals
goalcopy-dependencies/goal
/goals
/plugin
That will only copy the assembly-descriptor dependencies of your module
On Sun, Feb 24, 2008 at 9:09 PM, Stephen Connolly
[EMAIL PROTECTED] wrote:
Copy requires that the artifact must be in the local repository or in a
remote repository.
The copy dependencies allows for the artifact to come from the reactor, so
you don't have to install the artifact into your local repository.
The copy dependencies can be set to only copy one dependency.
Trust me, this is the better way to do it.
-Stephen
On Sat, Feb 23, 2008 at 9:38 PM, Reto Bachmann-Gmür [EMAIL PROTECTED] wrote:
Thank you very much for your help, I can now have many projects generate
the right assembly with just one assembly descriptor and without
requiring to check out multiple projects (and having them at the right
position in the directory structure).
I don't understand your suggestion to use copy-dependencies, what I'm
doing is copying a single resource (the assembly descriptor) and not all
of the dependencies. The copy goal seems to do its job.
Cheers,
reto
Stephen Connolly wrote:
there are two sets of goals in the maven dependency plugin.
the first set are copy and unpack. you specify the artifacts inside
the plugin configuration. these are not the set you want. the set you
want are copy-dependencies (or something like that I am on my iPod so
you will have to check) with this set you add the dependency to the
pom. that will force maven to sequence things correctly for you.
the build helper plugin has a default phase, so leave that alone. I
would bind the dependency plugin to one of the generate phases
(sources or resources)
Stephen
2/22/08, Reto Bachmann-Gmür [EMAIL PROTECTED] wrote:
The version I posted doesn't work as the child-projects can't perform
the attach-artifact attached to the package phase.
I've now extracted the dist configuration and the attachment of it to
a
separate project[1]. Having done this I also attached the copy and
the
assembly goals to the compile and package phases [2].
1.
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps-assembly/trunk/pom.xml
2. in
http://knobot.svn.sourceforge.net/svnroot/knobot/rwcf-apps/trunk/pom.xml
Reto Bachmann-Gmür wrote:
Thanks Stephen,
trying to follow the path you describe I added the following to the
parent-pom:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuild-helper-maven-plugin/artifactId
executions
execution
idattach-artifacts/id
phasepackage/phase
goals
goalattach-artifact/goal
/goals
configuration
artifacts
artifact
filesrc/assembly/dist.xml/file
typexml/type
classifier
assembly-descriptor
/classifier
/artifact
/artifacts
/configuration
/execution
/executions
/plugin
and
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
artifactItems
artifactItem
groupIdorg.wymiwyg.rwcf/groupId
artifactIdrwcf-apps/artifactId
version0.0.1/version
typexml/type
classifierassembly-descriptor/classifier
overWritefalse/overWrite
outputDirectory
${project.build.directory}/src/assembly/
/outputDirectory
destFileNamedist.xml/destFileName
/artifactItem
/artifactItems
/configuration
/plugin
furthermore I changed the descriptor of maven-assembly-plugin to use
${project.build.directory}/src/assembly/dist.xml. I didn't change
anything to the child-projects.
I can now execute mvn clean dependency:copy assembly:assembly for
child projects to create a distribution-package.
The only thing which I'm still insecure is about attaching this to
phases, the difficulty seems that the super project doesn't need to
have this attached to any phase, and the dependency resolution fails
unless executed after install (a solution might be to split the
parent
into a grand-parent providing the assembly descriptor and binding it
to phases in the intermediate parent). But I'm not sure anyway in
which phase to best create zip and tar.
Cheers,
reto
Stephen Connolly wrote:
You could attach the common descriptor as a build artifact one
module, and
then use the dependency plugin to pull it down to each child
module.
i.e.
Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a
classifier of, e.g. assembly-descriptor.
Now when you run mvn install or mvn deploy
Multi-Module Hierarchy : Eclipse vs Maven Plugins
Greetings All, I've been part of a team of happy Eclipse Ant+(Some 'Glue') developer for many years, from which I now have replaced the Ant+(Some 'Glue') with maven. I couldn't find any comprehensive articles on this, hence the email: The default eclipse flat project structure is in direct contradiction to the default maven hierarchy structure. This seems to lead to the situation where you're damned if you do, and damned if you don't. Firstly, when you stick with the default maven hierarchy structure all sorts of things automagically just work! Please don't pretend they all work with flat/other structure, they don't. No one can even speak on behalf of ALL plugin's and claim they do work. But, there's an awful lot of awesome only works with default hierarchy maven plugin's and tools because they make this simple assumption. The real problem is that these awesome plugins and tools are so valuable to development that you really really really should stick with the default maven hierarchy structure! On the inverse: Eclipse has been around for many years. It's comprised of some pretty awesome plugin's, tools yadda yadda yadda please don't say use netbeans or IDEA they're not the issue here. Eclipse does the opposite to maven, it expects a flat project structure and just like the Maven plugin's, if you deviate from this you start discarding awesome features within eclipse that you would consider mandatory for your development environment. One of the major problems with eclipse (and is not addressed on the maven website), is how a hierarchy structure works with your SCM (cvs or svn). This is something most would say is mandatory! If you checkout the parent, then you also checkout the modules contained within it. Then if you say ok lets check out the modules now... then you break the structure. The bottom line is that eclipse can't cope with specifically with the parent and heirarchy strucutre. You must checkout the whole parent with command line (or a different IDE) and mvn install the parent to the local repo.. then work on each module individually checked out in isolation. Unless someone can explain how I can checkout a parent with modules.. see each project (inc parent) as an eclipse project and run the parent goals inside the IDE.. then the best solution for eclipse maven is. Hierarchy and complex/manual eclipse usage.
Re: Multi-Module Hierarchy : Eclipse vs Maven Plugins
Andrew Hughes wrote: The bottom line is that eclipse can't cope with specifically with the parent and heirarchy strucutre. You must checkout the whole parent with command line (or a different IDE) and mvn install the parent to the local repo.. Yep, not too far beyond most developers at this point... then work on each module individually checked out in isolation. Why? Just run mvn eclipse:eclipse in the root of your multimodule project, and then tell eclipse to import existing projects starting at the root of the multi module project. Eclipse will import all projects regardless of any weird directory structure you (or maven) might have imposed, and you can switch between the projects at will, and have all of them loaded at once. Maven sets up all the eclipse projects in a multimodule build so that each project depends directly on each other project in eclipse (as opposed to modules depending on the final jar of another module). This removes the need to run mvn install on one module before changes to it are visible to other modules in the multimodule project. Yes, the original checkout will need to be done outside of eclipse using a normal scm tool, but that's not beyond the skills of a developer is it? Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: [ANN] Maven Stage Plugin 1.0-alpha-1 Released
Muy bueno, para sincronizar repositorios de maven... On Sat, Feb 23, 2008 at 12:38 AM, Wendy Smoak [EMAIL PROTECTED] wrote: The Maven team is pleased to announce the first release of the Maven Stage Plugin, version 1.0-alpha-1. http://maven.apache.org/plugins/maven-stage-plugin/ This plugin assists with staging and promoting releases by allowing you to copy artifacts from one repository to another. It currently supports copying from http|https to scp urls. You can run 'mvn -up stage:copy ... ' to get the latest version of the plugin. (Nothing was closed in JIRA for this initial release, so there are no release notes.) Enjoy, -- Wendy Smoak on behalf of the Maven team
generating checksums and gpg signing
To create md5 and sha1 hashes, and gpg signatures, we added (in a POM profile that is conditionally activated) some maven things to sign (using maven-gpg-plugin) and do checksums (using maven-install-plugin, version 2.2, which has a createChecksum flag). It isn't quite working right. The gpg plugin runs during verify lifecycle, right before install - in order to put the xxx.asc file into the /target, so install can copy it to the local repo. The install:install runs after that, and computes the md5 and sha1 checksums on everything, *including the xxx.asc file*. Unlike the gpg plugin, it does *not* put these files into /target, but only puts them into the local maven repository. I see other projects have figured out how to do this so the checksums are not added to the xxx.asc (gpg signature) files. How is this done? -Marshall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM
mevenide for eclipse is for maven 1 only. Milos On Sun, Feb 24, 2008 at 8:52 PM, Chris [EMAIL PROTECTED] wrote: How about mevenide? Has anyone used it, know how it compares? Carlos Sanchez wrote: i've added a list of Q4E features to the table On Sun, Feb 24, 2008 at 10:04 AM, [EMAIL PROTECTED] wrote: Since the question of choosing an Eclipse Integration is often asked, I just worked on the Eclipse Integration page from Maven Users Wiki: http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration I started a comparison matrix with basic project informations. This Wiki is public: feel free to improve the comparison. Selon Abel Muiño [EMAIL PROTECTED]: As for the comparison between maven integration solutions, I know none but it would be interesting if someone started one (like a google group and some pages on it). Since I'm involved with q4e, it would not be a fair comparison if I made it :-). I think it would be easy to have a feature matrix just if several users of the different solutions exchanged opinions on a list. As for cleaning the project from the shell... if you use eclipse, you'll need to refresh/rebuild the workspace. This is not a problem with the plug-ins, but something that goes deep in the eclipse architecture. Rodrigo Madera wrote: Since you are on the topic, do you know if any of these have trouble if you go to a shell and do a `mvn clean` on the project? I have a plugin (dont remember its name) that integrates Maven nicely, but is allergic to the (sometimes needed) cleaning. Thanks, Rodrigo On Sun, Feb 24, 2008 at 2:09 AM, Jason Chaffee [EMAIL PROTECTED] wrote: I found the following FAQ about Q4E: http://code.google.com/p/q4e/wiki/FAQ Features * running Maven goals from the IDE * dependency managing using the Maven POM, with automatic download of dependencies * keeping Eclipse classpath synchronized with Maven POM * dependency graphing http://code.google.com/p/q4e/wiki/DependencyGraphViewer * direct import of Maven 2 projects * wizard for creation of new projects using the archetype mechanism * modular approach to improve reusability by other Eclipse projects * ability to import parent projects (pom projects) http://code.google.com/p/q4e/wiki/ImportingMultiprojects (from 0.5.0) * ability to cancel maven builds (from 0.5.0) * dependency analysis tooling (from 0.5.0) What are the differences between this plugin and m2eclipse (aka Tycho)? The objective of this plugin is to be part of the Eclipse Foundation http://www.eclipse.org , for that reason the license is EPL and we are going to follow the foundation procedures. Thanks to the sponsorship of DevZuz http://www.devzuz.com , an Eclipse Strategic Developer Member http://www.eclipse.org/membership/showMember.php?member_id=824 we are in a good position to achieve this goal. Besides the objective, there are technical differences. While m2eclipse shows Maven output in a console, Q is based in events and will show them in an organized way that allows filtering by severity, search,... Functionality like the dependency graph, or creation of new projects using the archetype mechanism are only present in Q. Also it's implemented in several modules with reusability and extension in mind so other people can develop their own plugins taking advantage of the functionality they need (see for instance Candy for Appfuse http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be -under-extreme-refactoring/http://ramblingabout.wordpress.com/2007/09/02/candy-for-appfuse-will-be-under-extreme-refactoring/ ). In any case the underlying Maven libraries used for both plugins are the same (the Maven Embedder) and both plugin developers collaborate in its development. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, February 23, 2008 5:45 PM To: users@maven.apache.org Subject: Mevenide vs. M2Eclipse, Q for Eclipse/IAM I googled around to try to find a comparison between Mevenide and the alternatives, and didn't come up with much. Can someone tell me the differences? (I've spend some time with m2eclipse, and I'm *not* impressed).
Re: Multi-Module Hierarchy : Eclipse vs Maven Plugins
Thanks Graham! I works this out just as I got your email :) To explain this to others... taking a multi module maven project either out of svn/cvs (Q: outside eclipse only?) or creating one from scratch leaves you with a skeleton Maven project. With no eclipse .project/.classpath/.whatever files in the project, it can then be made eclipse complient with the mvn eclipse:eclipse command on the project parent. From this point onwards, the project source now contains all the Maven Information, Eclipse Information, and possibly svn/cvs. Now that you have content to import, you can Import Existing Projects - Maven Project into Eclipse. With it will come the Maven, Eclipse and possibly svn/cvs information. The parent appears in the project list, as do the modules. I only have these closing questions/clarification... Performing checkout's outside the IDE, then running mvn eclipse:eclipse, then importing is a bit of a pain to get around this would people (arguably no doubt) checkin the mvn eclipse:eclipse configuration into svn/cvs once generated? Or is it possible to checkout a parent, then run eclipse:eclipse within the IDE? Thanks again, Andrew On Mon, Feb 25, 2008 at 9:52 AM, Graham Leggett [EMAIL PROTECTED] wrote: Andrew Hughes wrote: The bottom line is that eclipse can't cope with specifically with the parent and heirarchy strucutre. You must checkout the whole parent with command line (or a different IDE) and mvn install the parent to the local repo.. Yep, not too far beyond most developers at this point... then work on each module individually checked out in isolation. Why? Just run mvn eclipse:eclipse in the root of your multimodule project, and then tell eclipse to import existing projects starting at the root of the multi module project. Eclipse will import all projects regardless of any weird directory structure you (or maven) might have imposed, and you can switch between the projects at will, and have all of them loaded at once. Maven sets up all the eclipse projects in a multimodule build so that each project depends directly on each other project in eclipse (as opposed to modules depending on the final jar of another module). This removes the need to run mvn install on one module before changes to it are visible to other modules in the multimodule project. Yes, the original checkout will need to be done outside of eclipse using a normal scm tool, but that's not beyond the skills of a developer is it? Regards, Graham --
Re: Is it possible to make some delaying between surefire plugin executions?
For 1) also check that you shutting down the db in the tearDown (if you don't already do this of course). Found hsqldb to require a clean shutdown and it fixed things for me. Cheers, Johan Dan Fabulich wrote: vetalok wrote: 1. Is it possible to add some delaying between few execution phases of surefire plugin, e.g 10 seconds (hsqldb says: .lck file is locked by another process)? Not really. Much easier to add a Thread.sleep() line to your tests. 2. Is it possible to run my surefire executions in the same JVM across all executions?. You've already set forkMode=never, which should do that by virtue of never spawning another JVM. Do you find it's not doing that? -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- you too? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
