Re: maven-eclipse-plugin install-plugins and source-jars
Hello, On Wed, 17 Sep 2008 15:13:31 +0200, Lars Fischer [EMAIL PROTECTED] mail.org said: I use the maven-eclipse-plugin with the goal install-plugins to create an eclipse target-platform containing my bundle-dependencies. Is is also possible to get the sources of these dependencies into this platform-folder following the same renaming rules like the binary-jars? Am I the only one who needs the sources of the used bundles? Is there a plan for extending the plugin for such a goal? regards, Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is this mailing list really slow for anyone else?
On Thursday 18 September 2008 Leszek Gawron wrote: Baptiste MATHUS wrote: Did you check if your mail was present in the public archive to see if it could be a problem with your server, and what hour your message was registered ? See http://www.nabble.com/Maven---Users-f178.html for example. maybe the emails simply require manual moderation and this causes the delay... I don't think so. Usually my mails show up within the next minute. - martin signature.asc Description: This is a digitally signed message part.
Re: maven-eclipse-plugin install-plugins and source-jars
Hello, On Fri, 19 Sep 2008 08:24:09 +0200, Lars Fischer I use the maven-eclipse-plugin with the goal install-plugins to create an eclipse target-platform containing my bundle-dependencies. Is is also possible to get the sources of these dependencies into this platform-folder following the same renaming rules like the binary-jars? I tried to integrate a MANIFEST.MF with the needed Eclipse-SourceBundle- header into the source-jar. But I found no way to do this. The maven-source- plugin generates a small new MANIFEST.MF and has no option to configure an other file for it. regards, Lars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven 2.1.0-M1 Released
Hi John,
I don't find the 2.1.0-M1 in the download page.
Is there a problem or maybe it's just some cron that hasn't updated the page
yet with the newly released version?
Cheers
2008/9/19 John Casey [EMAIL PROTECTED]
The Maven team is pleased to announce the release of the Maven 2.1.0-M1.
This release signals the beginning of a new direction in the development of
Maven. Recently, Maven's development efforts were split into three major
goals. First, the Maven 2.0.x code line will be minimally maintained for
regression fixes; the 2.0.x series should be entering end-of-life mode soon
now that 2.1.0-M1 is out.
Next, the 2.x series aims to accomplish a relatively conservative series of
new features, improved implementations, and other changes that bring with
them too much risk to be appropriate for a revision release on the 2.0.x
version series. Each of these releases - 2.1, 2.2, and so on - will be
preceded by a formal release plan.
Finally, the 3.x series is the home of Maven's more aggressive
improvements, including wholesale reimplementation of subsystems and the
introduction of major new features.
This means that all discussions in the past that referred to Maven 2.1 now
apply mainly to Maven 3.x, currently under development. We will backport
some of the smaller features to the 2.x version series, provided we can
contain the risk of these features and provide a smooth transition from one
version to the next for the user.
You can download Maven here:
http://maven.apache.org/download.html
Release Notes - Maven 2 - Version 2.1.0-M1
** Bug
* [MNG-2068] - Multiple inheritance fails to find grand parent in
../../pom.xml when the groupIds differ (Test Case Attached)
* [MNG-2318] - When a project has modules and its parent is not
preinstalled the build fails
* [MNG-2695] - -o makes build fail for snapshot plugins
* [MNG-2739] - Repository entries are not validated and NPE will occur
* [MNG-2873] - Unable to find transitive dependencies when they have
been relocated.
* [MNG-3052] - Transitive Dependency not found when repo is not listed
* [MNG-3070] - ${x} properties no longer expanded in /version tag
after 2.0.3
* [MNG-3106] - Multiple profile activation conditions broken
* [MNG-3368] - Printing version (-v argument) should not stop lifecycle
execution
* [MNG-3380] - MavenMetadataSource retrieves ResolutionGroup without
consulting ManagedVersionMap, is problem when relocation
* [MNG-3475] - Some directories are not basedir aligned
* [MNG-3482] - merging managed dependencies happens before
managed-dependency versions are interpolated
* [MNG-3497] - rar, par and ejb3 archives should not be added to
classpath
* [MNG-3498] - StringIndexOutOfBounds -1 during path translation while
reading pom.xml
* [MNG-3527] - profile deactivation has no affect
* [MNG-3530] - Regression: Properties get resolved before the LifeCycle
is Forked.
* [MNG-3535] - Valid properties which look self referential fail to
resolve
* [MNG-3536] - REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it
doesn't work anymore
* [MNG-3545] - Option -P-profile overridden if profile is
activebyDefault
* [MNG-3581] - stage:copy ClassCastException with maven 2.0.9
* [MNG-3584] - possible new memory leak in Maven 2.0.9
* [MNG-3585] - nonProxyHosts separator is wrong in the default
settings.xml
* [MNG-3599] - webdav does not set http-proxy correctly
* [MNG-3622] - upgrade to wagon 1.0-beta-4
* [MNG-3639] - Ant 1.7.0 Task not found after upgrading from Maven 2.0.8
to 2.0.9
* [MNG-3642] - back-propagation of resources doesn't handle multiple
resources with the same directory
* [MNG-3645] - Maven doesn't do strict model validation for POMs in the
current reactor
* [MNG-3651] - mvn.bat returns an incorrect error code
* [MNG-3654] - [regression] unable to build ServiceMix 3 -
IndexOutOfBoundsException in mergeDeterministicBuildElements
* [MNG-3667] - Dependencies resolution is wrong in some cases
(xfire-core:1.2.6 for example)
* [MNG-3671] - plugin-level dependencies in POMs are not interpolated at
correct time
* [MNG-3679] - executionid${some.custom.var}/id ... broke
* [MNG-3680] - POM validation fails on projects in central repo starting
with 2.0.10 RCs
* [MNG-3684] - Injection of Build instance as report parameter results
in uninterpolated values for build.directory, etc.
* [MNG-3693] - Updating project POM via project.setFile(..) changes
project basedir, and project classpath when used as a dependency in a
reactor
* [MNG-3694] - plugin parameters injecting ${project.compileSourceRoots}
get uninterpolated source directories
* [MNG-3697] - NPE at DefaultPluginManager line 700 (from Hudson CI)
* [MNG-3701] - ClassCastException when building settings.xml with
profiles that have activeByDefault set
* [MNG-3703] - ExecutionProject contains relative
release plugin with submodules
Hi, I am trying the release plugin on a project with sub-modules within Eclipse. The project is named 'core' and the sub-module is 'plugin-setproperties'. I want to release only one sub-module, not the whole project. I go into the sub-module project and execute release:prepare. This works, sub-module is tagged in cvs and release.properties is created. Then I execute release:perform which does not work: - Cvs checks out the whole project, not only the tagged sub-project. CVS checkout normally works in a way that the directories that do not belong to the tag are deleted at the end. This does not happen - The deploy ends with an error saying a pom is missing. Maybe there is missing a 'change directory' to go into the sub-module directory? [INFO] Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/cvs/remotepayment -q checkout -r plugin-setproperties-0_0_2 -d checkout core [INFO] Working directory: D:\projekte\core\plugin-setproperties\target [DEBUG] Executing CVS command: checkout -r plugin-setproperties-0_0_2 -d checkout core [DEBUG] [DEBUG] [DEBUG] U checkout/plugin-setproperties/.cvsignore [DEBUG] U checkout/plugin-setproperties/pom.xml [DEBUG] U checkout/plugin-setproperties/src/main/java/net/atos/wlp/core/setpropert ies/SetPropertiesMojo.java [DEBUG] U checkout/plugin-setproperties/src/main/resources/directory-info.txt [DEBUG] U checkout/plugin-setproperties/src/main/resources/log4j.properties [INFO] Executing goals 'deploy'... [INFO] Executing: mvn deploy --no-plugin-updates -DperformRelease=true -f pom.xml [INFO] Scanning for projects... [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [deploy] [INFO] [INFO] Ignoring available plugin update: 2.5 as it requires Maven version 2.0.9 [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one. Kind regards Wolfgang Winter
error about import maven 2.09 source to m2eclipse
there is a mistake when I trying to import maven source code to my project user m2eclipse plugin, the error like the attachment pic. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven 2.1.0-M1 Released
2008/9/19 Baptiste MATHUS [EMAIL PROTECTED]:
Hi John,
I don't find the 2.1.0-M1 in the download page.
Is there a problem or maybe it's just some cron that hasn't updated the page
yet with the newly released version?
It's below Maven 2.0.9.
However I did notice a problem with the site since it was deployed,
will update it again now.
- Brett
Cheers
2008/9/19 John Casey [EMAIL PROTECTED]
The Maven team is pleased to announce the release of the Maven 2.1.0-M1.
This release signals the beginning of a new direction in the development of
Maven. Recently, Maven's development efforts were split into three major
goals. First, the Maven 2.0.x code line will be minimally maintained for
regression fixes; the 2.0.x series should be entering end-of-life mode soon
now that 2.1.0-M1 is out.
Next, the 2.x series aims to accomplish a relatively conservative series of
new features, improved implementations, and other changes that bring with
them too much risk to be appropriate for a revision release on the 2.0.x
version series. Each of these releases - 2.1, 2.2, and so on - will be
preceded by a formal release plan.
Finally, the 3.x series is the home of Maven's more aggressive
improvements, including wholesale reimplementation of subsystems and the
introduction of major new features.
This means that all discussions in the past that referred to Maven 2.1 now
apply mainly to Maven 3.x, currently under development. We will backport
some of the smaller features to the 2.x version series, provided we can
contain the risk of these features and provide a smooth transition from one
version to the next for the user.
You can download Maven here:
http://maven.apache.org/download.html
Release Notes - Maven 2 - Version 2.1.0-M1
** Bug
* [MNG-2068] - Multiple inheritance fails to find grand parent in
../../pom.xml when the groupIds differ (Test Case Attached)
* [MNG-2318] - When a project has modules and its parent is not
preinstalled the build fails
* [MNG-2695] - -o makes build fail for snapshot plugins
* [MNG-2739] - Repository entries are not validated and NPE will occur
* [MNG-2873] - Unable to find transitive dependencies when they have
been relocated.
* [MNG-3052] - Transitive Dependency not found when repo is not listed
* [MNG-3070] - ${x} properties no longer expanded in /version tag
after 2.0.3
* [MNG-3106] - Multiple profile activation conditions broken
* [MNG-3368] - Printing version (-v argument) should not stop lifecycle
execution
* [MNG-3380] - MavenMetadataSource retrieves ResolutionGroup without
consulting ManagedVersionMap, is problem when relocation
* [MNG-3475] - Some directories are not basedir aligned
* [MNG-3482] - merging managed dependencies happens before
managed-dependency versions are interpolated
* [MNG-3497] - rar, par and ejb3 archives should not be added to
classpath
* [MNG-3498] - StringIndexOutOfBounds -1 during path translation while
reading pom.xml
* [MNG-3527] - profile deactivation has no affect
* [MNG-3530] - Regression: Properties get resolved before the LifeCycle
is Forked.
* [MNG-3535] - Valid properties which look self referential fail to
resolve
* [MNG-3536] - REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it
doesn't work anymore
* [MNG-3545] - Option -P-profile overridden if profile is
activebyDefault
* [MNG-3581] - stage:copy ClassCastException with maven 2.0.9
* [MNG-3584] - possible new memory leak in Maven 2.0.9
* [MNG-3585] - nonProxyHosts separator is wrong in the default
settings.xml
* [MNG-3599] - webdav does not set http-proxy correctly
* [MNG-3622] - upgrade to wagon 1.0-beta-4
* [MNG-3639] - Ant 1.7.0 Task not found after upgrading from Maven 2.0.8
to 2.0.9
* [MNG-3642] - back-propagation of resources doesn't handle multiple
resources with the same directory
* [MNG-3645] - Maven doesn't do strict model validation for POMs in the
current reactor
* [MNG-3651] - mvn.bat returns an incorrect error code
* [MNG-3654] - [regression] unable to build ServiceMix 3 -
IndexOutOfBoundsException in mergeDeterministicBuildElements
* [MNG-3667] - Dependencies resolution is wrong in some cases
(xfire-core:1.2.6 for example)
* [MNG-3671] - plugin-level dependencies in POMs are not interpolated at
correct time
* [MNG-3679] - executionid${some.custom.var}/id ... broke
* [MNG-3680] - POM validation fails on projects in central repo starting
with 2.0.10 RCs
* [MNG-3684] - Injection of Build instance as report parameter results
in uninterpolated values for build.directory, etc.
* [MNG-3693] - Updating project POM via project.setFile(..) changes
project basedir, and project classpath when used as a dependency in a
reactor
* [MNG-3694] - plugin parameters injecting ${project.compileSourceRoots}
get uninterpolated source directories
* [MNG-3697] - NPE at DefaultPluginManager line 700
Re: [ANN] Maven 2.1.0-M1 Released
I just tried downloading it by non of the mirrors I tried seemed to have it - I gave up after about 10 mirrors - will try downloading again in a few hours, probably just taking its time to propagate.. On Fri, Sep 19, 2008 at 8:13 PM, Brett Porter [EMAIL PROTECTED]wrote: However I did notice a problem with the site since it was deployed, will update it again now. -- It is easier to optimize correct code than to correct optimized code. -- Bill Harlan
Re: [ANN] Maven 2.1.0-M1 Released
Well that isn't too surprising since it's not in the download area at all (!) I've copied it across form the deployed repository and it should be syncing shortly... - Brett 2008/9/19 Mark Derricutt [EMAIL PROTECTED]: I just tried downloading it by non of the mirrors I tried seemed to have it - I gave up after about 10 mirrors - will try downloading again in a few hours, probably just taking its time to propagate.. On Fri, Sep 19, 2008 at 8:13 PM, Brett Porter [EMAIL PROTECTED]wrote: However I did notice a problem with the site since it was deployed, will update it again now. -- It is easier to optimize correct code than to correct optimized code. -- Bill Harlan -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
release-plugin: execute at generate-sources phase
Hi all, i need to filter a resource file before the generate-sources phase (input file for source-generator). So i bound the maven-resources-plugin to the generate-sources phase. The point is that filtering does not work anymore. Even the filtering in the default lifecycle-phase of the generator plugin does not work anymore. Seem as explicity naming the resource-plugin overwrites some default configuration. Any idea which one this could be? Or any other idea how this could be solved.. Thanks, Klaus --- build plugins plugin artifactIdmaven-resources-plugin/artifactId executions execution idfilterGeneratorInput/id phasegenerate-sources/phase goals goalresources/goal /goals configuration resources resource filteringtrue/filtering directorysrc/main/resources/directory includes includeGeneratorInput.xml/include /includes /resource /resources outputDirectorytarget\klaus/outputDirectory /configuration /execution /executions configuration resources resource filteringtrue/filtering directorysrc/main/resources/META-INF/directory /resource /resources /configuration /plugin !-- (Re-)Generate -- plugin artifactIdmyGeneratorPlugin/artifactId ...
How can we get this pom.xml?
I down load Maven 2.09 source code from https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9 but in the pom.xml of the top fold, I see the parent segment like this: parent groupIdorg.apache.maven/groupId artifactIdmaven-parent/artifactId version8/version relativePath../pom/maven/pom.xml/relativePath /parent where should i find the ./pom/maven/pom.xml thank you
Re: How can we get this pom.xml?
It should be here: https://svn.apache.org/repos/asf/maven/pom/tags/maven-parent-9/ Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Sep 19, 2008 at 11:48 AM, 陈思淼 [EMAIL PROTECTED] wrote: I down load Maven 2.09 source code from https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9 but in the pom.xml of the top fold, I see the parent segment like this: parent groupIdorg.apache.maven/groupId artifactIdmaven-parent/artifactId version8/version relativePath../pom/maven/pom.xml/relativePath /parent where should i find the ./pom/maven/pom.xml thank you
Re: How can we get this pom.xml?
thanks for your help 2008/9/19 Nick Stolwijk [EMAIL PROTECTED] It should be here: https://svn.apache.org/repos/asf/maven/pom/tags/maven-parent-9/ Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Sep 19, 2008 at 11:48 AM, 陈思淼 [EMAIL PROTECTED] wrote: I down load Maven 2.09 source code from https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9 but in the pom.xml of the top fold, I see the parent segment like this: parent groupIdorg.apache.maven/groupId artifactIdmaven-parent/artifactId version8/version relativePath../pom/maven/pom.xml/relativePath /parent where should i find the ./pom/maven/pom.xml thank you
RE: a slue of warnings
Is there a way I can update my maven pom that has a dependency on this somewhere such that I'm getting the latest version of plexus? We are trying to migrate to these new machines and having almost 38K lines of nonsense makes it impossible to build in CC. mvn -q makes things so quiet, it's useless. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2008 1:18 AM To: Maven Users List Subject: Re: a slue of warnings As the Jira MNG says: This issue has already been fixed in PLX-287. This MNG issue is to try and get that fix into 2.0.x So, the bug still exists in Maven, though it has been fixed in Plexus... The fix has simply never made its way into a Maven release, as yet. Wayne On Thu, Sep 18, 2008 at 2:56 PM, EJ Ciramella [EMAIL PROTECTED] wrote: So I'm very confused - This bug says it's NOT fixed http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugi n Yet, this one says it is: http://jira.codehaus.org/browse/PLX-287 Where can I see the version of plexus used? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2008 12:12 PM To: Maven Users List Subject: Re: a slue of warnings 2008/9/16 EJ Ciramella [EMAIL PROTECTED] Which component - SystemPropertyProfileActivator? How do I shut it off via the logger? It's generating (as shown below) almost 39 thousand lines so it can't simply be ignored. Apologies, I was thinking of something else. This can only be changed programatically. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2008 7:50 PM To: Maven Users List Subject: Re: a slue of warnings I believe it can be safely ignored. You might like to try editing the Maven installation's logger configuration to not output warnings from this component. - Brett 2008/9/16 Michael Delaney [EMAIL PROTECTED] All, We have been using Maven 2.0.9 for sometime but on a Windows environment (Windows 2000 Windows XP). We are beginning our testing to move from Windows to Solaris. When I try to do a 'mvn clean install' on one of our projects, we get a slue (count of 38772) warnings that are all [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileA c ti [EMAIL PROTECTED]. We found a bug (pasted below) but I wanted to hit up the mailing list to see if anyone could shed some light on the situation. Help? [ Maven Bug ] http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugin. system.issuetabpanels:comment-tabpanelfocusedCommentId=134786#action _ 13 http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plu g in .system.issuetabpanels:comment-tabpanelfocusedCommentId=134786#actio n _1 3 4786 -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trouble about siteDirectory
Hi everybody, I'm using the stage-deploy of site plugin, everything works fine and no error message is shown; unfortunately, some resources such the rss checksyle and changes plugin's images are not present in the specified siteDirectory. Is there some config param I miss? My POM doesn't contain any information about distribution management - AFAIK is not required to stage a site. Any help will be very well appreciated, thanks in advance. Best regards, Simone -- My LinkedIn profile: http://www.linkedin.com/in/simonetripodi My GoogleCode profile: http://code.google.com/u/simone.tripodi/ My Picasa: http://picasaweb.google.com/simone.tripodi/ My Tube: http://www.youtube.com/user/stripodi My Del.icio.us: http://del.icio.us/simone.tripodi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem with release:prepare in resolving dependency
I'm a newbie with the release plugin and have a hard time already managing dependencies. After much thinking, I end up with this process: - branch first the current trunk version to a branch named 1.0-SNAPSHOT. The trunk version becomes 1.1-SNAPSHOT - release the branch version: the release is the 1.0 version, the branch becomes 1.0.1-SNAPSHOT I need the branch step first in order to be able to fix bug that could appear on the 1.0 version. A tag not being modifiable, I need to be able to rerelease from the 1.0-SNAPSHOT line. And so came the idea of the 1.0.1-SNAPSHOT version. If anyone has another solution for this problem, he is much welcome! Anyways, while trying this I'm confronted to a Maven release-plugin problem: I'm trying to release a component that depends only on the company-parent.pom (that follows the 1-SNAPSHOT - 2-SNAPSHOT release numbering pattern) I want the development version to be updated to depend on the released version 1 or 1.1-SNAPSHOT of the company-parent pom. here's the trace of the command: mvn release:prepare -DdryRun=true [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building commons-xml [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : Resolve Project Dependency Snapshots.: 'com.company:company-parent' set to release? (yes/no) yes: : What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1 What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1.1-SNAPSHOT What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 2-SNAPSHOT What is the release version for commons-xml? (com.company.commons:commons-xml) 1.0: : What is SCM release tag or label for commons-xml? (com.company.commons:commons-xml) commons-xml-1.0: : What is the new development version for commons-xml? (com.company.commons:commons-xml) 1.1-SNAPSHOT: : 1.0.1-SNAPSHOT [INFO] Transforming 'commons-xml'... [INFO] Not generating release POMs [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones [INFO] Executing goals 'clean verify'... [INFO] Executing: mvn clean verify --no-plugin-updates [INFO] Scanning for projects... [INFO] [INFO] Building commons-xml [INFO]task-segment: [clean, verify] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 2 source files to /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] No tests to run. [INFO] [jar:jar] [INFO] Building jar: /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target/stageof.jar [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [INFO]
Enunciate problem
Hi, I get the following warnings when I run 'mvn install' on my project. I think it's related to enunciate. [WARNING] WARNING: Unknown artifact 'client.jdk14.library.binaries'. Artifact will not be exported. [WARNING] War artifact 'spring.war.file' not found in the project... The generated war doesn't work when deployed with Tomcat. This is Tomcat's localhost log file: Sep 18, 2008 12:35:11 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Error configuring application listener of class org.codehaus.enunciate.modules.spring_app.SpringComponentPostProcessor java.lang.ClassNotFoundException: org.codehaus.enunciate.modules.spring_app.SpringComponentPostProcessor at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3786) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Sep 18, 2008 12:35:11 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Skipped installing application listeners due to previous error(s)
Re: How can we get this pom.xml?
On Fri, Sep 19, 2008 at 2:48 AM, 陈思淼 [EMAIL PROTECTED] wrote: I down load Maven 2.09 source code from https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9 but in the pom.xml of the top fold, I see the parent segment like this: parent groupIdorg.apache.maven/groupId artifactIdmaven-parent/artifactId version8/version relativePath../pom/maven/pom.xml/relativePath /parent where should i find the ./pom/maven/pom.xml thank you It should be retrieved from the central repo: http://repo1.maven.org/maven2/org/apache/maven/maven-parent/8/ -- Wendy
RE: Enunciate problem
this appears to be specific to the version of enunciate you're using please contact enunciate users group at [EMAIL PROTECTED] With Warm Regards, Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Date: Fri, 19 Sep 2008 09:43:08 -0400 From: [EMAIL PROTECTED] To: users@maven.apache.org Subject: Enunciate problem Hi, I get the following warnings when I run 'mvn install' on my project. I think it's related to enunciate. [WARNING] WARNING: Unknown artifact 'client.jdk14.library.binaries'. Artifact will not be exported. [WARNING] War artifact 'spring.war.file' not found in the project... The generated war doesn't work when deployed with Tomcat. This is Tomcat's localhost log file: Sep 18, 2008 12:35:11 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Error configuring application listener of class org.codehaus.enunciate.modules.spring_app.SpringComponentPostProcessor java.lang.ClassNotFoundException: org.codehaus.enunciate.modules.spring_app.SpringComponentPostProcessor at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3786) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Sep 18, 2008 12:35:11 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Skipped installing application listeners due to previous error(s) _ See how Windows connects the people, information, and fun that are part of your life. http://clk.atdmt.com/MRT/go/msnnkwxp1020093175mrt/direct/01/
Re: Maven Windows
I don't understand why it worked all day and then failed right before I left. There were always spaces and the path was always that long. Oh, I understand what happened. I formatted the pom. I hate spaces in paths. This is from the last build that succeeded: file://C:/Program Files (x86)/Apache Group/Apache2/htdocs/maven/ - Session: Opened file://C:/Program Files (x86)/Apache Group/Apache2/htdocs/maven/ - Session: Disconnecting file://C:/Program Files (x86)/Apache Group/Apache2/htdocs/maven/ - Session: Disconnected This is from the last build that failed: file://C:/Program Files (x86)/Apache Group/Apache2/htdocs/maven/ - Session: Disconnecting file://C:/Program Files (x86)/Apache Group/Apache2/htdocs/maven/ - Session: Disconnected [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error uploading site Embedded error: Repository path C:\Program Files (x86)\Apache Group\Apache2\htdocs\maven does not exist, and cannot be created. On Thu, Sep 18, 2008 at 8:05 PM, Brett Porter [EMAIL PROTECTED]wrote: Hard to tell without more information, but you can get similar things with paths that are too long, for example (though I think the message is different to doesn't exist). The other problem might be spaces. - Brett 2008/9/19 Jon Strayer [EMAIL PROTECTED]: I've been using Maven for about seven years now without any real problems. I just changed jobs and now instead of a Unix server for the build server I'm got a Windows server. Today a build failed saying that the directory it was supposed to dump the generated web site to didn't exist. It didn't have any trouble finding it the build before. And the directory does exist. I've never seen anything like that before. Is it a Windows thing? -- Esse Quam Videre To Be, rather than to Seem -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Esse Quam Videre To Be, rather than to Seem
Having trouble with setting a property in settings.xml and activating a profile in a pom based on that property
Hello All, I'm trying to set a property in the settings.xml file and then have a profile in the pom.xml file activate if that property is set. Right now I don't care about the value, I just need it to be set. Currently I have the following in my settings.xml file. profile idA/id activation activeByDefaulttrue/activeByDefault /activation properties davidC:\temp/david /properties /profile In my pom.xml I have the following. profiles profile idB/id activation property namedavid/name /property /activation ... profiles I can see from running mvn help:active-profiles that profile A in the settings.xml file is active but profile B is not. I can also use the David property in other areas of the pom file. I'm I doing something wrong? I'm using Maven-2.0.6 on Windows. Thanks, David
[Need Help] Re: jar artifact contains more classes than desired.
I have got closer to why it is happening. I wrote a small dtrace[1]
script to monitor open system calls for those additional class files. I
attached it to a build m/c and after around 150 builds, once it
occurred. Every time open system call was made with that file handle, I
print the java stack. The output of dtrace is attached here with. That
file got opened three times. As the stack suggests, first by
maven-compiler-plugin, then by maven-bundle-plugin and finally by
maven-jar-plugin. So, it is the compiler-plugin that is responsible for
creating that servlet class in jacc target dir. That is very surprising.
*Why would compiler-plugin compile dependencies? *Any clue?
Thanks,
Sahoo
[1] http://opensolaris.org/os/community/dtrace/
Sahoo wrote:
We are experiencing an issue in our build system and it is not
happening for every one. I used to think it only happens for mvn
2.0.8, but just now a developer told me that they see it mvn 2.0.7 as
well. For whatever reason, sometimes, a jar artifact is containing not
only the classes compiled from the sources that are part of that
artifact, it also contains dependent .class files. It is a very
serious problem for us. Given below is the artifact that's causing
trouble.
project ...
modelVersion4.0.0/modelVersion
parent
groupIdorg.glassfish/groupId
artifactIdapi-pom/artifactId
version10.0-SNAPSHOT/version
/parent
artifactIdjavax.security.jacc/artifactId
packagingjar/packaging
namejavax.security.jacc API v.1.2/name
dependencies
dependency
groupIdorg.glassfish/groupId
artifactIdjavax.servlet/artifactId
version${project.version}/version
/dependency
/dependencies
/project
As you can see, it depends on
org.glassfish:javax.servlet:10.0-SNAPSHOT, which is a jar type
artifact and contains javax.servlet classes. I can assure you that in
the source tree of javax.security.jacc module, there is no
javax.servlet class. Yet, javax.security.jacc-10.0-SNAPSHOT.jar
contains a bunch of javax.servlet classes. I should also state that it
only happens when both javax.servlet module and javax.security.jacc
module are part of same maven reactor. The build log produced with -X
option is quite large, so I am supplying log for jacc module portion
only. Pl. see the attachment called build.all.jacc.log. I will be
happy to supply more of it if need be. I should say, I don't
understand something from the log file. I am highlighting it here with
bold letters:
[INFO] Reactor build order:
...
[INFO] javax.servlet API v.3.0
[INFO] javax.security.jacc API v.1.2
...
[INFO]
[INFO] Building javax.servlet API v.3.0
[INFO]task-segment: [clean, install]
[INFO]
...
[INFO] Installing
/export/v3/v3/web/javax.servlet/target/javax.servlet-10.0-SNAPSHOT-sources.jar
to
/home/mvatkina/.m2/repository/org/glassfish/javax.servlet/10.0-SNAPSHOT/javax.servlet-10.0-SNAPSHOT-sources.jar
[INFO]
[INFO] Building javax.security.jacc API v.1.2
[INFO]task-segment: [clean, install]
[INFO]
...
[INFO] [clean:clean]
[INFO] Deleting directory
/export/v3/v3/security/javax.security.jacc/target
[DEBUG] org.glassfish:javax.security.jacc:jar:10.0-SNAPSHOT (selected
for null)
[DEBUG] junit:junit:jar:4.3.1:test (selected for test)
[DEBUG] active project artifact:
*artifact =
org.glassfish:javax.servlet:jar:10.0-SNAPSHOT:compile;
project: MavenProject:
org.glassfish:javax.servlet:10.0-SNAPSHOT @
/export/v3/v3/web/javax.servlet/pom.xml (selected for compile)
*
What does this active project artifact mean? By looking at the
attached log file, do you have any suggestion for me?
Thanks,
Sahoo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
0 94114 open64:entry
libc.so.1`__open64+0x15
libc.so.1`open64+0x72
libhpi.so`0xd0f2221b
libjvm.so`JVM_Open+0x3a
libjava.so`0xd0e9c3f0
libjava.so`Java_java_io_FileOutputStream_open+0x2b
java/io/FileOutputStream.open
java/io/FileOutputStream.init
java/io/FileOutputStream.init
com/sun/tools/javac/jvm/ClassWriter.writeClass
com/sun/tools/javac/main/JavaCompiler.genCode
com/sun/tools/javac/main/JavaCompiler.compile
com/sun/tools/javac/main/Main.compile
com/sun/tools/javac/main/Main.compile
com/sun/tools/javac/Main.compile
StubRoutines (1)
Archiva Build Problem
Here is my error message. Solaris 10 SPARC apache-tomcat-6.0.18 archiva 1.1.2 Sep 19, 2008 10:45:01 AM org.springframework.web.context.ContextLoader initWebApplicationContext SEVERE: Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'urlFailureCache' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'cache#url-failures-cache' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cache#url-failures-cache': Post-processing of the FactoryBean's object failed; nested exception is net.sf.ehcache.CacheException: Error configuring from file:/export/home/archiva/apache-tomcat-6.0.18/webapps/ROOT/WEB-INF/classes/ehcache.xml. Initial cause was Error configuring from input stream. Initial cause was Attribute name CacheManager associated with an element type ehcache must be followed by the ' = ' character. at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104) at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:464) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:156) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:855) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:765) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:412) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:926) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:889) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at
Re: Archiva Build Problem
On Fri, Sep 19, 2008 at 9:34 AM, waaraa1331 [EMAIL PROTECTED] wrote: Here is my error message. Solaris 10 SPARC apache-tomcat-6.0.18 archiva 1.1.2 Archiva has separate mailing lists... you can find subscription info on this page: http://archiva.apache.org/mail-lists.html (I haven't tried it in Tomcat, but there is some info here: http://archiva.apache.org/docs/1.1.2/adminguide/webapp.html ) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-eclipse-plugin JRE classpath generation problem
Hi, I have some problem. I am trying to create eclipse project using 'mvn eclipse:eclipse' command. My configuration of maven-eclipse-plugin is below: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId configuration buildcommands buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand buildcommandorg.eclipse.mtj.core.preverifier/buildcommand /buildcommands projectnatures projectnatureorg.eclipse.jdt.core.javanature/projectnature projectnatureorg.eclipse.mtj.core.nature/projectnature /projectnatures classpathContainers classpathContainerorg.elipse.mtj.JavaMEContainer/Sun Java(TM) Wireless Toolkit 2.5.2 for CLDC/DefaultColorPhone/classpathContainer /classpathContainers /configuration /plugin With this configuration I get .classpath file like this: classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src path=src/main/resources excluding=**/*.java/ classpathentry kind=output path=target/classes/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=con path=org.elipse.mtj.JavaMEContainer/Sun Java(TM) Wireless Toolkit 2.5.2 for CLDC/DefaultColorPhone/ /classpath The problem is I would like to get rid of JRE in classpath because I use JavaME. So my question is how to set maven-eclipse-plugin to not generate this line: classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ Cheers, Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archiva Build Problem
You should really be able to parse that stack trace and find the error... Hint: look for the word initial cause. Wayne On Fri, Sep 19, 2008 at 9:40 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Fri, Sep 19, 2008 at 9:34 AM, waaraa1331 [EMAIL PROTECTED] wrote: Here is my error message. Solaris 10 SPARC apache-tomcat-6.0.18 archiva 1.1.2 Archiva has separate mailing lists... you can find subscription info on this page: http://archiva.apache.org/mail-lists.html (I haven't tried it in Tomcat, but there is some info here: http://archiva.apache.org/docs/1.1.2/adminguide/webapp.html ) -- Wendy - 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: a slue of warnings
According to what JvZ and Brian said in the bug, it doesn't seem to be a trivial dependency change, or I'd expect it might have already been done. Andy looked into this and we can't fix it easily without upgrading the container and that's just too much work... we can try to upgrade the container which will bring people in line with 2.1 but will require much testing. So, I doubt that simply changing the Plexus version in a pom somewhere will do it. You should try the latest 2.1.0-M1 and see if the bug is still there. Wayne On Fri, Sep 19, 2008 at 3:31 AM, EJ Ciramella [EMAIL PROTECTED] wrote: Is there a way I can update my maven pom that has a dependency on this somewhere such that I'm getting the latest version of plexus? We are trying to migrate to these new machines and having almost 38K lines of nonsense makes it impossible to build in CC. mvn -q makes things so quiet, it's useless. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2008 1:18 AM To: Maven Users List Subject: Re: a slue of warnings As the Jira MNG says: This issue has already been fixed in PLX-287. This MNG issue is to try and get that fix into 2.0.x So, the bug still exists in Maven, though it has been fixed in Plexus... The fix has simply never made its way into a Maven release, as yet. Wayne On Thu, Sep 18, 2008 at 2:56 PM, EJ Ciramella [EMAIL PROTECTED] wrote: So I'm very confused - This bug says it's NOT fixed http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugi n Yet, this one says it is: http://jira.codehaus.org/browse/PLX-287 Where can I see the version of plexus used? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2008 12:12 PM To: Maven Users List Subject: Re: a slue of warnings 2008/9/16 EJ Ciramella [EMAIL PROTECTED] Which component - SystemPropertyProfileActivator? How do I shut it off via the logger? It's generating (as shown below) almost 39 thousand lines so it can't simply be ignored. Apologies, I was thinking of something else. This can only be changed programatically. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2008 7:50 PM To: Maven Users List Subject: Re: a slue of warnings I believe it can be safely ignored. You might like to try editing the Maven installation's logger configuration to not output warnings from this component. - Brett 2008/9/16 Michael Delaney [EMAIL PROTECTED] All, We have been using Maven 2.0.9 for sometime but on a Windows environment (Windows 2000 Windows XP). We are beginning our testing to move from Windows to Solaris. When I try to do a 'mvn clean install' on one of our projects, we get a slue (count of 38772) warnings that are all [WARNING] Component returned which is not the same manager. Ignored. component=org.apache.maven.profiles.activation.SystemPropertyProfileA c ti [EMAIL PROTECTED]. We found a bug (pasted below) but I wanted to hit up the mailing list to see if anyone could shed some light on the situation. Help? [ Maven Bug ] http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugin. system.issuetabpanels:comment-tabpanelfocusedCommentId=134786#action _ 13 http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plu g in .system.issuetabpanels:comment-tabpanelfocusedCommentId=134786#actio n _1 3 4786 -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - 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] - 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]
m2eclipse and inter-module dependencies...
We've got a multi-module maven-based project and we're trying to import it using m2eclipse. Everything seems to be working fine, but it's not setting up the classpath correctly for projects that depend on other projects, it seems. Is this a known issue? -- View this message in context: http://n2.nabble.com/m2eclipse-and-inter-module-dependencies...-tp1101616p1101616.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: m2eclipse and inter-module dependencies...
Never saw that. Workspace projects won't be resolved either if you have workspace resolution disabled or if dependency versions won't match projects in workspace. Also note that dependent projects should have Maven support enabled. Anyway, it is better to ask questions specific to m2eclipse in m2eclipse users mailing list. See http://m2eclipse.codehaus.org/mail-lists.html regards, Eugene jwcarman wrote: We've got a multi-module maven-based project and we're trying to import it using m2eclipse. Everything seems to be working fine, but it's not setting up the classpath correctly for projects that depend on other projects, it seems. Is this a known issue? -- View this message in context: http://www.nabble.com/m2eclipse-and-inter-module-dependencies...-tp19577444p19577759.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]
Including Local Jar Files in Build Classpath
I want to include some local jar files (located in lib/) in my Maven build classpath. How do I do that? MG Michael McGrady Senior Engineer Topia Technology, Inc. [EMAIL PROTECTED] 1 (253) 720-3365 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Including Local Jar Files in Build Classpath
Hello Michael, Maybe you should consider a more Maven way, of installing those libraries into your local repository by using Maven's install plugin and its install-file mojo, and then adding them as dependencies in your project's POM. Check thishttp://maven.apache.org/plugins/maven-install-plugin/usage.htmllink on Maven install plugin usage. Regards, Stevo. On Fri, Sep 19, 2008 at 10:55 PM, Michael McGrady [EMAIL PROTECTED] wrote: I want to include some local jar files (located in lib/) in my Maven build classpath. How do I do that? MG Michael McGrady Senior Engineer Topia Technology, Inc. [EMAIL PROTECTED] 1 (253) 720-3365 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven/Eclipse - Keeping them in sync?
I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven/Eclipse - Keeping them in sync?
Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven/Eclipse - Keeping them in sync?
Hello David, Just as Klaus said, use m2eclipse plugin. After installing it, I'd first manually create a folder in eclipse workspace, named as your root maven project artifactId, then copy root POM and rest of the project structure you've created into that new folder. Finally, with m2eclipse plugin you could just File--Import...--General--Maven Projects and select/browse to newly created folder, leaving m2eclipse do the rest. Regards, Stevo. On Fri, Sep 19, 2008 at 11:24 PM, Klaus [EMAIL PROTECTED] wrote: Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Including Local Jar Files in Build Classpath
store at location used by maven.repo.local http://maven.apache.org/maven-1.x/plugins/jar/properties.html e.g. localRepository/path/to/local/repository/localRepository ]]/configuration descriptionThe ArtifactRepository instance referencing the local artifact repository./description cliOptions cliOption key-Dmaven.repo.local=/path/to/local/repo/key valueOverride the local repository location on a per-build basis./value or of course pass in as command line parameter .. HTH Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. From: [EMAIL PROTECTED] To: users@maven.apache.org Subject: Including Local Jar Files in Build Classpath Date: Fri, 19 Sep 2008 13:55:35 -0700 I want to include some local jar files (located in lib/) in my Maven build classpath. How do I do that? MG Michael McGrady Senior Engineer Topia Technology, Inc. [EMAIL PROTECTED] 1 (253) 720-3365 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ See how Windows Mobile brings your life together—at home, work, or on the go. http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/
Re: Maven/Eclipse - Keeping them in sync?
What about doing a right click in the Project Explorer, select New - Other ... - Maven - Maven Project ? Then in the New Maven Project window only check Use default Workspace location, click Next, then you get that glorious list of Archetypes to choose from. Stevo Slavi? wrote: Hello David, Just as Klaus said, use m2eclipse plugin. After installing it, I'd first manually create a folder in eclipse workspace, named as your root maven project artifactId, then copy root POM and rest of the project structure you've created into that new folder. Finally, with m2eclipse plugin you could just File--Import...--General--Maven Projects and select/browse to newly created folder, leaving m2eclipse do the rest. Regards, Stevo. On Fri, Sep 19, 2008 at 11:24 PM, Klaus [EMAIL PROTECTED] wrote: Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - 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: Maven/Eclipse - Keeping them in sync?
Thanks for the tips, guys. I had forgotten about the m2eclipse plugin. It's been too long since I was in a real project. :-) I guess m2eclipse has come a little further since I last looked at it - probably 2 years? Thanks again, Dave Stevo Slavic' wrote: Hello David, Just as Klaus said, use m2eclipse plugin. After installing it, I'd first manually create a folder in eclipse workspace, named as your root maven project artifactId, then copy root POM and rest of the project structure you've created into that new folder. Finally, with m2eclipse plugin you could just File--Import...--General--Maven Projects and select/browse to newly created folder, leaving m2eclipse do the rest. Regards, Stevo. On Fri, Sep 19, 2008 at 11:24 PM, Klaus [EMAIL PROTECTED] wrote: Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - 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: Maven/Eclipse - Keeping them in sync?
You also could give it a try to q4E: http://code.google.com/p/q4e/ It has a lot of very nice features... M2Eclipse and q4E have both very nice features... And both have their projects at Eclipse: http://www.eclipse.org/proposals/m2e/ http://www.eclipse.org/proposals/iam/ And they both have approved projects http://www.eclipse.org/m2e/ http://www.eclipse.org/iam/ I wonder why the Eclipse Foundation guys didn't merge both projects... On Fri, Sep 19, 2008 at 4:00 PM, David C. Hicks [EMAIL PROTECTED] wrote: Thanks for the tips, guys. I had forgotten about the m2eclipse plugin. It's been too long since I was in a real project. :-) I guess m2eclipse has come a little further since I last looked at it - probably 2 years? Thanks again, Dave Stevo Slavic' wrote: Hello David, Just as Klaus said, use m2eclipse plugin. After installing it, I'd first manually create a folder in eclipse workspace, named as your root maven project artifactId, then copy root POM and rest of the project structure you've created into that new folder. Finally, with m2eclipse plugin you could just File--Import...--General--Maven Projects and select/browse to newly created folder, leaving m2eclipse do the rest. Regards, Stevo. On Fri, Sep 19, 2008 at 11:24 PM, Klaus [EMAIL PROTECTED] wrote: Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - 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] -- (o_ \* / / ) | / \ / | O | v v
Separate Jar FIles
I have a project in which separate applications are included for ease of development due to their dependencies. I want Maven to create separate SNAPSHOTS for each. How do I do that? Or, better, where do I look? Mike Michael McGrady Senior Engineer Topia Technology, Inc. [EMAIL PROTECTED] 1 (253) 720-3365 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Separate Jar FIles
On Fri, Sep 19, 2008 at 3:47 PM, Michael McGrady [EMAIL PROTECTED] wrote: I have a project in which separate applications are included for ease of development due to their dependencies. I want Maven to create separate SNAPSHOTS for each. How do I do that? Or, better, where do I look? If by a project you mean a single source tree, you'll probably need to break it up into separate modules. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: improve Maven performance
Hi, You can have a look to this plugin https://maven-incremental-build.dev.java.net/ I know it doesn't solve completely the problem but now after a modification or an update from scm, you can compile without a clean and be sure that all the children of a modified module will be recompiled. Now, our builds are safe and their times is more often than 5 minutes rather than 11 or 12, depends if modifications are in hight level modules or not. I still search the way to block the build process for modules with no modifications on her dependencies so if someone has more informations on how achieve it, it would be fine. Vincent On Wed, Sep 17, 2008 at 10:56 PM, Yann [EMAIL PROTECTED] wrote: Hi, In our company lot of people complains that our maven 2 builds are too long. We use multi modules and most of the time we only need to build 1 or 2 modules not all of them. So a solution could be to create a Maven 2 plugin that will check if a source file has changed in the module. If no file has changed then it will skip all other phases of the module (from generate-sources to packaging...). So I know how to bind a plugin to the first maven phase (validate). But how to skip all others phases without interrupted the multi-module build ? Thanks Yann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven/Eclipse - Keeping them in sync?
megathor wrote: You also could give it a try to q4E: http://code.google.com/p/q4e/ It has a lot of very nice features... M2Eclipse and q4E have both very nice features Here is side by side comparison http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration megathor wrote: And both have their projects at Eclipse: http://www.eclipse.org/proposals/m2e/ http://www.eclipse.org/proposals/iam/ I wonder why the Eclipse Foundation guys didn't merge both projects... Eclipse Foundation does not interfere with project development, it only provides infrastructure, legal support and general coordination. Basically it is up to project developers to decide to join forces, but there is a lot of code in both m2eclipse and q4e projects and it is unclear how one would merge those different codebases. regards, Eugene -- View this message in context: http://www.nabble.com/Maven-Eclipse---Keeping-them-in-sync--tp19579618p19581094.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: Maven/Eclipse - Keeping them in sync?
OK, I installed m2eclipse and it seems happy with my project. I was able to go through the POM editor and update a lot of information that previously wasn't there. Very cool. Problem: I still don't see it picking up new source folders. If I add a source folder in Eclipse, how does that end up in the pom.xml to somehow be included in a production and/or test build? I see a spot to enter source folders in the POM editor, but it is unclear how to actually enter them. Am I missing something? Thanks again! Dave PS - for those who recommended Q4E, I'm looking at it, too, but from what I can tell it seems that m2eclipse is way ahead in terms of fit and finish. That's just a first impression, though. Stevo Slavic' wrote: Hello David, Just as Klaus said, use m2eclipse plugin. After installing it, I'd first manually create a folder in eclipse workspace, named as your root maven project artifactId, then copy root POM and rest of the project structure you've created into that new folder. Finally, with m2eclipse plugin you could just File--Import...--General--Maven Projects and select/browse to newly created folder, leaving m2eclipse do the rest. Regards, Stevo. On Fri, Sep 19, 2008 at 11:24 PM, Klaus [EMAIL PROTECTED] wrote: Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - 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: Maven/Eclipse - Keeping them in sync?
To bring project up to date when adding source directories, try selecting the following menu item from the contextual menu (right-click on your project in the Package Explorer): Maven = Update Project Configuration This will synch up the source folders with the Eclipse classpath. David C. Hicks wrote: OK, I installed m2eclipse and it seems happy with my project. I was able to go through the POM editor and update a lot of information that previously wasn't there. Very cool. Problem: I still don't see it picking up new source folders. If I add a source folder in Eclipse, how does that end up in the pom.xml to somehow be included in a production and/or test build? I see a spot to enter source folders in the POM editor, but it is unclear how to actually enter them. Am I missing something? Thanks again! Dave PS - for those who recommended Q4E, I'm looking at it, too, but from what I can tell it seems that m2eclipse is way ahead in terms of fit and finish. That's just a first impression, though. Stevo Slavic' wrote: Hello David, Just as Klaus said, use m2eclipse plugin. After installing it, I'd first manually create a folder in eclipse workspace, named as your root maven project artifactId, then copy root POM and rest of the project structure you've created into that new folder. Finally, with m2eclipse plugin you could just File--Import...--General--Maven Projects and select/browse to newly created folder, leaving m2eclipse do the rest. Regards, Stevo. On Fri, Sep 19, 2008 at 11:24 PM, Klaus [EMAIL PROTECTED] wrote: Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - 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] -- View this message in context: http://www.nabble.com/Maven-Eclipse---Keeping-them-in-sync--tp19579618p19582428.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: Maven/Eclipse - Keeping them in sync?
No, that doesn't work. It just resets the source folders to what the Maven pom.xml thinks it should be. I had tried that before, but I just double-checked before I replied to make certain I wasn't misremembering. Thanks for the suggestion, though. stug23 wrote: To bring project up to date when adding source directories, try selecting the following menu item from the contextual menu (right-click on your project in the Package Explorer): Maven = Update Project Configuration This will synch up the source folders with the Eclipse classpath. David C. Hicks wrote: OK, I installed m2eclipse and it seems happy with my project. I was able to go through the POM editor and update a lot of information that previously wasn't there. Very cool. Problem: I still don't see it picking up new source folders. If I add a source folder in Eclipse, how does that end up in the pom.xml to somehow be included in a production and/or test build? I see a spot to enter source folders in the POM editor, but it is unclear how to actually enter them. Am I missing something? Thanks again! Dave PS - for those who recommended Q4E, I'm looking at it, too, but from what I can tell it seems that m2eclipse is way ahead in terms of fit and finish. That's just a first impression, though. Stevo Slavic' wrote: Hello David, Just as Klaus said, use m2eclipse plugin. After installing it, I'd first manually create a folder in eclipse workspace, named as your root maven project artifactId, then copy root POM and rest of the project structure you've created into that new folder. Finally, with m2eclipse plugin you could just File--Import...--General--Maven Projects and select/browse to newly created folder, leaving m2eclipse do the rest. Regards, Stevo. On Fri, Sep 19, 2008 at 11:24 PM, Klaus [EMAIL PROTECTED] wrote: Have a look at http://m2eclipse.codehaus.org . It's a eclipse plugin that updates the project settings according to the setting in the pom.xml. No (re)generate of eclipse-project files, no problem with new source folders.. klaus On Fri, Sep 19, 2008 at 11:17 PM, David C. Hicks [EMAIL PROTECTED] wrote: I'm beginning a new, fairly large, project. Eclipse will be our development platform, but I've already set up the starting point in Maven. Simple enough. Now, my question is, how can I keep them in sync, easily? I realize that it's best to re-run mvn eclipse:eclipse after adding dependencies, but what about source folders? I need to add new source folders, but Maven doesn't know anything about that, so the next time I re-generate the .project/.classpath files, it'll revert back to those folders not being source folders. Any help how to make this behave? Thanks, Dave - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
