from:"Eric Miles \(JIRA\)"

[jira] (MECLIPSE-441) Packaging type maven-plugin causes unresolved dependencies in multi-module build

2013-07-12 Thread Eric Miles (JIRA)


[ 
https://jira.codehaus.org/browse/MECLIPSE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=328492#comment-328492
 ] 

Eric Miles commented on MECLIPSE-441:
-

We have this same issue as well, but it happens on a module that has ear 
packaging.  The other modules in the reactor work fine (jar and war)

 Packaging type maven-plugin causes unresolved dependencies in multi-module 
 build
 --

 Key: MECLIPSE-441
 URL: https://jira.codehaus.org/browse/MECLIPSE-441
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Bug
  Components: Core : Dependencies resolution and build path 
 (.classpath), Core : Multi-projects
Affects Versions: 2.5.1
 Environment: Linux 2.6 (Xubuntu 8.0)
Reporter: Alex Rau
 Attachments: maven_bug.tar.bz2


 Attached a sample project setup.
 How to reproduce:
 - untar attachment
 - cd into reactor folder
 - call mvn eclipse:eclipse
 Artifact x:project_plugin cannot be resolved, however the dependency and the 
 modules set is correct.
 As soon as the packaging type of the maven-plugin is changed to jar it 
 works as expected.
 Installing the maven-plugin project first is perhaps a workaround (a bad one, 
 not tried yet). Makes however a clean/from scratch multi-module build in 
 eclipse very ugly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MDEP-423) Can not unpack dependencies from identified dependent POM without specifying version

2013-07-03 Thread Eric Miles (JIRA)

Eric Miles created MDEP-423:
---

 Summary: Can not unpack dependencies from identified dependent POM 
without specifying version
 Key: MDEP-423
 URL: https://jira.codehaus.org/browse/MDEP-423
 Project: Maven 2.x Dependency Plugin
  Issue Type: Bug
  Components: unpack
Affects Versions: 2.8
Reporter: Eric Miles


Even if the dependency from the included POM is in the dependency tree, I can 
not unpack it unless I specify the version...which defeats the purpose of an 
aggregator POM.

aggregator-pom.xml
{noformat}
...
groupIdmycompany.com/groupId
artifactIdaggregator-pom/artifactId
version1.0.0/version
packagingpom/packaging
...
dependency
groupIdsomegroup/groupId
artifactIdsomeartifact/artifactId
version1.2.3/version
/dependency
...
{noformat}

pom-to-do-unpacking.xml
{noformat}
...
dependency
groupIdmycompany.com/groupId
artifactIdaggregator-pom/artifactId
version1.0.0/version
packagingpom/packaging
/dependency
...
plugin
artifactIdmaven-dependency-plugin
goals
goalunpack/goal
/goal
configuration
artifactItems
artifactItem
groupIdsomegroup/groupId
artifactIdsomeartifact/artifactId
!-- Will not work without version 
specified -
/artifactItem
/artifactItems
/configuration
...
/plugin
...
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-08-24 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232946#action_232946
]

Eric Miles commented on MRELEASE-261:
-

Michael,

While the flat structure is supported, it's very particular about how it's
structured. I wrote a series of blog posts on this. The third in the series
can be found at the following link, and that post has pointers to the first 2
(I recommend reading them in order).

[http://ericmiles.wordpress.com/2010/02/08/maven-release-non-supported-scm-structures/]

release:prepare should support flat directory multi-module projects
---

Key: MRELEASE-261
URL: http://jira.codehaus.org/browse/MRELEASE-261
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: prepare
Environment: linux / maven2 / svn
Reporter: paul.whe...@gmail.com
Assignee: Maria Odea Ching
Fix For: 2.0

Attachments: flatProject.main.patch, flatProject.test.patch,
maven-release-issue.tar.gz, maven-release-issue.zip,
MRELEASE-261-sample-project.zip, MRELEASE-261-with-its-v3.patch,
MRELEASE-261-with-its.patch, MRELEASE-261.patch, odd-tags.png,
PrepareReleaseMojo.patch

What I mean by flat file structure firstly.
parent/pom.xml
module1/pom.xml
module2/pom.xml
.
.
.
module15/pom.xml
the parent references the modules like so
modules
module../module1/module
module../module2/module
.
.
.
module../module15/module
/modules
When i release:prepare only the parent project is tagged the modules
projects versions are incremented etc but the modules are not tagged in svn.
I use this structure as i use eclipse as my IDE.
I would love to see a fix for the issue marked as closed here
http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand
each submodule of the projects but it would be so nice to have the release
plugin do this for me.
forgive my english.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MRELEASE-516) release:prepare should support a nested/flat hybrid SCM structure

2010-01-20 Thread Eric Miles (JIRA)

release:prepare should support a nested/flat hybrid SCM structure
-

 Key: MRELEASE-516
 URL: http://jira.codehaus.org/browse/MRELEASE-516
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
  Components: perform, prepare
Affects Versions: 2.0-beta-9
 Environment: OS X 10.5.8, Windows XP Prof, JDK 1.5.0_12, SVN, GIT, CVS
Reporter: Eric Miles
 Attachments: maven-release-issue.zip, odd-tags.png

This issue is related to MRELEASE-261 in that release prepare is having some 
difficulty in dealing with certain SCM structures during the prepare goal.  Our 
project structure is flat as you would see in a typical IDE setup:

{noformat}
release-workspace\
|
|--release-parent
||+pom.xml (modules: ../release-module1, ../release-module2)
|
|--release-module1
||+pom.xml (parent: ../release-parent)
|
|--release-module2
 |+pom.xml (parent: ../release-parent)
{noformat}

Our SCM (svn) structure is as follows:
{noformat}
svnroot
|
+--release-parent/trunk/pom.xml
+--release-parent/tags/release-parent-1.0.9/pom.xml
|
+--release-module1/trunk/pom.xml
+--release-module1/tags/release-module1-1.0.9/pom.xml
|
+--release-module1/trunk/pom.xml
+--release-module2/tags/release-module2-1.0.9/pom.xml
{noformat}

If we execute release:prepare with no configuration to the release plugin, we 
get the following error:
{noformat}
[INFO] [INFO] 

[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd 
/Users/emiles/Projects/release-workspace/release-parent  svn 
--non-interactive commit --file 
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-1253932520.commit 
--targets 
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-4376558781490229966-targets
[INFO] Working directory: 
/Users/emiles/Projects/release-workspace/release-parent
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{noformat}

If we use the 2.0-beta-10-SNAPSHOT with flat project support and provide the 
-DcommitByProject=true JVM parameter, we do not get any errors, however tagging 
does not happen as expected.  Rather than having tags for each of the projects, 
some odd tagging happened at the parent level where an entire structure was 
created (with branches, tags and trunk under the tag folder).  I'm attaching a 
screen shot for reference.

Ignoring the fact that the prepare only somewhat worked, when I attempted to 
perform the release, I get an error:
{noformat}
emiles-macbook:release-parent emiles$ mvn release:perform -DcommitByProject=true
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO]   Unnamed - com.captechventures:release-module1:jar:0.0.3-SNAPSHOT
[INFO]   Unnamed - com.captechventures:release-module2:jar:0.0.3-SNAPSHOT
[INFO] 
[INFO] Building Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO] 
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd 
/Users/emiles/Projects/release-workspace/release-parent/target  svn 
--non-interactive checkout 
http://localhost/dev/release-parent/tags/release-parent-0.0.2 
/Users/emiles/Projects/release-workspace/release-parent/target/checkout
[INFO] Working directory: 
/Users/emiles/Projects/release-workspace/release-parent/target
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
[WARNING] Maven will be executed in interactive mode, but no input stream has 
been configured for this MavenInvoker instance.
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error executing Maven.

Working directory 
/Users/emiles/Projects/release-workspace/release-parent/target/checkout/Users/emiles/Projects/release-workspace/release-parent
 does not exist!
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 5 seconds
[INFO] Finished at: Mon Jan 04

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-20 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207633#action_207633
]

Eric Miles commented on MRELEASE-261:
-

New issue created, and mentioned in the description.

MRELEASE-516

release:prepare should support flat directory multi-module projects
---

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-19 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207493#action_207493
]

Eric Miles commented on MRELEASE-261:
-

Dennis,

So I guess you're saying that it's impossible for the release plugin to support
the following SVN structure (or there are no future plans to support it)?

{noformat}
svnroot
|
+--release-parent/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
{noformat}

The reason I ask is I am often brought on client/projects LONG after their SVN
repos are setup and whether or not they can use the release plugin (especially
for large projects) would be a big determinator for me in a Maven
recommendation. Trust me, I'd prefer if clients could/would reposition their
SVN repo and existing projects so multi-module builds just worked.

release:prepare should support flat directory multi-module projects
---

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-19 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207493#action_207493
]

Eric Miles edited comment on MRELEASE-261 at 1/19/10 10:08 AM:
---

Dennis,

So I guess you're saying that it's impossible for the release plugin to support
the following SVN structure (or there are no future plans to support it)?

{noformat}
svnroot
|
+--release-parent/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
{noformat}

It sounds like the definition of a flat structure in this particular test case
is all projects flattened behind a single trunk/branch/tag. My use case are
the projects are flattened at the SVN root level, but each have their own
trunk/branches/tags. It seems as though my use case is a hybrid of the typical
maven setup and the flattened use case you have provided.

was (Author: bigehokie):
Dennis,

So I guess you're saying that it's impossible for the release plugin to support
the following SVN structure (or there are no future plans to support it)?

{noformat}
svnroot
|
+--release-parent/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
{noformat}

release:prepare should support flat directory multi-module projects
---

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-19 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207519#action_207519
]

Eric Miles commented on MRELEASE-261:
-

Dennis,

No problem with the questions. When I get enough time, I'll create a new JIRA
and reference here in the comments.

I wish I could answer why they have setup their repositories this way, I
certainly would have steered them otherwise if I had been there during initial
infrastructure setup. My current client I'm pushing to move to the more
traditional nested model for Maven multi-module projects, but it's not a quick
process. One multi-module build of theirs contains over 36 modules (and an
obvious candidate for breaking into smaller project)!

Thanks again for your help.

release:prepare should support flat directory multi-module projects
---

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-18 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207361#action_207361
]

Eric Miles commented on MRELEASE-261:
-

Dennis,

Yes, you are correct in that's the structure. I'm not sure how flat
multi-module projects are usually stored in SVN, however, I'm a consultant and
have been on 3 different clients/projects i the last 2 years and all 3 of these
clients had their subversion repo setup this way (were setup LONG before I got
there).

Regardless, I would think the release plugin would work appropriately no matter
what my SVN structure is considering that metadata is provided in the POM. I
would think it shouldn't care how it's stored in SVN (or any SCM for that
matter) nor should it care what structure it is in as long as the parent pom is
available (in the reactor or available via relativePath).

release:prepare should support flat directory multi-module projects
---

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-18 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207361#action_207361
]

Eric Miles edited comment on MRELEASE-261 at 1/18/10 7:02 PM:
--

Dennis,

I'm guessing that's a false assumption at this point :)

was (Author: bigehokie):
Dennis,

release:prepare should support flat directory multi-module projects
---

[jira] Updated: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-04 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eric Miles updated MRELEASE-261:

Attachment: maven-release-issue.zip

A zip archive of the sample project I have provided

release:prepare should support flat directory multi-module projects
---

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-04 Thread Eric Miles (JIRA)


[ 
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205002#action_205002
 ] 

Eric Miles commented on MRELEASE-261:
-

Dennis,

I know this isn't a working directory.  This is the eclipse workspace folder 
that contains the three projects and is the parent directory to the parent pom 
project.  Here is my directory structure:


{noformat}
release-workspace\
|
|--release-parent
||+pom.xml (modules: ../release-module1, ../release-module2)
|
|--release-module1
||+pom.xml (parent: ../release-parent)
|
|--release-module2
 |+pom.xml (parent: ../release-parent)
{noformat}

I am issuing the release:prepare from the release-parent directory, so there 
should be no reason I receive this error.

I have asked a coworker on a Windows box to pull down the sample project 
attachment, he had no problems opening it with 7zip.  In any case, I'm 
attaching another sample project archived in a zip format.

 release:prepare should support flat directory multi-module projects
 ---

 Key: MRELEASE-261
 URL: http://jira.codehaus.org/browse/MRELEASE-261
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
  Components: prepare
 Environment: linux / maven2 / svn
Reporter: paul.whe...@gmail.com
Assignee: Maria Odea Ching
 Fix For: 2.0

 Attachments: flatProject.main.patch, flatProject.test.patch, 
 maven-release-issue.tar.gz, maven-release-issue.zip, 
 MRELEASE-261-sample-project.zip, MRELEASE-261-with-its-v3.patch, 
 MRELEASE-261-with-its.patch, MRELEASE-261.patch, PrepareReleaseMojo.patch


 What I mean by flat file structure firstly.
 parent/pom.xml
 module1/pom.xml
 module2/pom.xml
 .
 .
 .
 module15/pom.xml
 the parent references the modules like so
 modules
   module../module1/module
   module../module2/module
 .
 .
 .
   module../module15/module
 /modules
 When i  release:prepare only the parent project is tagged the modules 
 projects versions are incremented etc but the modules are not tagged in svn.
 I use this structure as i use eclipse as my IDE.
 I would love to see a fix for the issue marked as closed here 
 http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand 
 each submodule of the projects but it would be so nice to have the release 
 plugin do this for me.
 forgive my english.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-04 Thread Eric Miles (JIRA)


[ 
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205002#action_205002
 ] 

Eric Miles edited comment on MRELEASE-261 at 1/4/10 7:57 AM:
-

Dennis,

I know this isn't a working directory.  This is the eclipse workspace folder 
that contains the three projects and is the parent directory to the parent pom 
project.  Here is my directory structure:


{noformat}
release-workspace\
|
|--release-parent
||+pom.xml (modules: ../release-module1, ../release-module2)
|
|--release-module1
||+pom.xml (parent: ../release-parent)
|
|--release-module2
 |+pom.xml (parent: ../release-parent)
{noformat}

I am issuing the release:prepare from the release-parent directory, so there 
should be no reason I receive this error.

I have asked a coworker on a Windows box to pull down the sample project 
attachment, he had no problems opening it with 7zip.  In any case, I'm 
attaching another sample project archived in a zip format.  Please see 
http://jira.codehaus.org/secure/attachment/46726/maven-release-issue.zip
.

  was (Author: bigehokie):
Dennis,

I know this isn't a working directory.  This is the eclipse workspace folder 
that contains the three projects and is the parent directory to the parent pom 
project.  Here is my directory structure:


{noformat}
release-workspace\
|
|--release-parent
||+pom.xml (modules: ../release-module1, ../release-module2)
|
|--release-module1
||+pom.xml (parent: ../release-parent)
|
|--release-module2
 |+pom.xml (parent: ../release-parent)
{noformat}

I am issuing the release:prepare from the release-parent directory, so there 
should be no reason I receive this error.

I have asked a coworker on a Windows box to pull down the sample project 
attachment, he had no problems opening it with 7zip.  In any case, I'm 
attaching another sample project archived in a zip format.
  
 release:prepare should support flat directory multi-module projects
 ---

 Key: MRELEASE-261
 URL: http://jira.codehaus.org/browse/MRELEASE-261
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
  Components: prepare
 Environment: linux / maven2 / svn
Reporter: paul.whe...@gmail.com
Assignee: Maria Odea Ching
 Fix For: 2.0

 Attachments: flatProject.main.patch, flatProject.test.patch, 
 maven-release-issue.tar.gz, maven-release-issue.zip, 
 MRELEASE-261-sample-project.zip, MRELEASE-261-with-its-v3.patch, 
 MRELEASE-261-with-its.patch, MRELEASE-261.patch, PrepareReleaseMojo.patch


 What I mean by flat file structure firstly.
 parent/pom.xml
 module1/pom.xml
 module2/pom.xml
 .
 .
 .
 module15/pom.xml
 the parent references the modules like so
 modules
   module../module1/module
   module../module2/module
 .
 .
 .
   module../module15/module
 /modules
 When i  release:prepare only the parent project is tagged the modules 
 projects versions are incremented etc but the modules are not tagged in svn.
 I use this structure as i use eclipse as my IDE.
 I would love to see a fix for the issue marked as closed here 
 http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand 
 each submodule of the projects but it would be so nice to have the release 
 plugin do this for me.
 forgive my english.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-04 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205038#action_205038
]

Eric Miles commented on MRELEASE-261:
-

Dennis,

That is correct. The only operation performed is the release:prepare from
within an SVN managed folder (the parent POM project folder), which happens to
be a sub-folder of the folder SVN is complaining about..

release:prepare should support flat directory multi-module projects
---

[jira] Updated: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-04 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eric Miles updated MRELEASE-261:

Attachment: odd-tags.png

Screen shot of the odd tagging performed with the flat project structure

release:prepare should support flat directory multi-module projects
---

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-04 Thread Eric Miles (JIRA)


[ 
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205043#action_205043
 ] 

Eric Miles commented on MRELEASE-261:
-

Dennis,

The good news is that the prepare goal SOMEWHAT worked.  While it was able to 
change the POMs and check those in appropriately, however it failed on tagging 
the release.  Instead of having tag for each one of the modules (which is what 
I would expect), only the parent pom project was tagged and was tagged in an 
odd way.  I'm attaching a screenshot, but the tag contains a branches, tags, 
and trunk folder underneath the tag.  Take a look at the odd-tags.png file I 
have attached.

Ignoring the tagging issue, I attempted to perform the release itself.  At this 
point I received the same issue I was receiving before, before I added the 
-DcommitByProject JVM parameter you identifiedL

{noformat}
emiles-macbook:release-parent emiles$ mvn release:perform -DcommitByProject=true
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO]   Unnamed - com.captechventures:release-module1:jar:0.0.3-SNAPSHOT
[INFO]   Unnamed - com.captechventures:release-module2:jar:0.0.3-SNAPSHOT
[INFO] 
[INFO] Building Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO] 
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd 
/Users/emiles/Projects/release-workspace/release-parent/target  svn 
--non-interactive checkout 
http://localhost/dev/release-parent/tags/release-parent-0.0.2 
/Users/emiles/Projects/release-workspace/release-parent/target/checkout
[INFO] Working directory: 
/Users/emiles/Projects/release-workspace/release-parent/target
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
[WARNING] Maven will be executed in interactive mode, but no input stream has 
been configured for this MavenInvoker instance.
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error executing Maven.

Working directory 
/Users/emiles/Projects/release-workspace/release-parent/target/checkout/Users/emiles/Projects/release-workspace/release-parent
 does not exist!
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 5 seconds
[INFO] Finished at: Mon Jan 04 12:22:31 EST 2010
[INFO] Final Memory: 11M/20M
[INFO] 

{noformat}

I had a configuration that I followed from one of the test cases checked in, 
where the workingDirectory was specified in the configuration of the plugin.  
seen as follows:
{noformat}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0-beta-10-20091102.165928-8/version
configuration

workingDirectory${basedir}/target/checkout/workingDirectory

useReleaseProfiletrue/useReleaseProfile

allowTimestampedSnapshotstrue/allowTimestampedSnapshots
/configuration
/plugin
{noformat}

I thought maybe this was the reason for the error, so I removed the 
workingDirectory configuration, performed all my checkins, did a prepare and 
attempted to release again and I received the same error as what is identified 
as above (I'm assuming this directory is the default config).


 release:prepare should support flat directory multi-module projects
 ---

 Key: MRELEASE-261
 URL: http://jira.codehaus.org/browse/MRELEASE-261
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
  Components: prepare
 Environment: linux / maven2 / svn
Reporter: paul.whe...@gmail.com
Assignee: Maria Odea Ching
 Fix For: 2.0

 Attachments: flatProject.main.patch, flatProject.test.patch, 
 maven-release-issue.tar.gz, maven-release-issue.zip, 
 MRELEASE-261-sample-project.zip, MRELEASE-261-with-its-v3.patch, 
 MRELEASE-261-with-its.patch,

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-04 Thread Eric Miles (JIRA)


[ 
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=205043#action_205043
 ] 

Eric Miles edited comment on MRELEASE-261 at 1/4/10 11:36 AM:
--

Dennis,

The good news is that the prepare goal SOMEWHAT worked.  While it was able to 
change the POMs and check those in appropriately, however it failed on tagging 
the release.  Instead of having tag for each one of the modules (which is what 
I would expect), only the parent pom project was tagged and was tagged in an 
odd way.  I'm attaching a screenshot, but the tag contains a branches, tags, 
and trunk folder underneath the tag.  Take a look at the odd-tags.png file I 
have attached.

Ignoring the tagging issue, I attempted to perform the release itself.  This is 
the error I received:

{noformat}
emiles-macbook:release-parent emiles$ mvn release:perform -DcommitByProject=true
[INFO] Scanning for projects...
[INFO] Reactor build order: 
[INFO]   Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO]   Unnamed - com.captechventures:release-module1:jar:0.0.3-SNAPSHOT
[INFO]   Unnamed - com.captechventures:release-module2:jar:0.0.3-SNAPSHOT
[INFO] 
[INFO] Building Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO] 
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd 
/Users/emiles/Projects/release-workspace/release-parent/target  svn 
--non-interactive checkout 
http://localhost/dev/release-parent/tags/release-parent-0.0.2 
/Users/emiles/Projects/release-workspace/release-parent/target/checkout
[INFO] Working directory: 
/Users/emiles/Projects/release-workspace/release-parent/target
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
[WARNING] Maven will be executed in interactive mode, but no input stream has 
been configured for this MavenInvoker instance.
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error executing Maven.

Working directory 
/Users/emiles/Projects/release-workspace/release-parent/target/checkout/Users/emiles/Projects/release-workspace/release-parent
 does not exist!
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 5 seconds
[INFO] Finished at: Mon Jan 04 12:22:31 EST 2010
[INFO] Final Memory: 11M/20M
[INFO] 

{noformat}

I had a configuration that I followed from one of the test cases checked in, 
where the workingDirectory was specified in the configuration of the plugin.  
seen as follows:

{noformat}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0-beta-10-20091102.165928-8/version
configuration

workingDirectory${basedir}/target/checkout/workingDirectory

useReleaseProfiletrue/useReleaseProfile

allowTimestampedSnapshotstrue/allowTimestampedSnapshots
/configuration
/plugin
{noformat}

I thought maybe this was the reason for the error, so I removed the 
workingDirectory configuration, performed all my checkins, did a prepare and 
attempted to release again and I received the same error as what is identified 
as above (I'm assuming this directory is the default config).


  was (Author: bigehokie):
Dennis,

The good news is that the prepare goal SOMEWHAT worked.  While it was able to 
change the POMs and check those in appropriately, however it failed on tagging 
the release.  Instead of having tag for each one of the modules (which is what 
I would expect), only the parent pom project was tagged and was tagged in an 
odd way.  I'm attaching a screenshot, but the tag contains a branches, tags, 
and trunk folder underneath the tag.  Take a look at the odd-tags.png file I 
have attached.

Ignoring the tagging issue, I attempted to perform the release itself.  At this 
point I received the same issue I was receiving before, before I added the 
-DcommitByProject JVM parameter you identifiedL

{noformat}
emiles-macbook:release-parent emiles$ mvn

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

2010-01-03 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204976#action_204976
]

Eric Miles commented on MRELEASE-261:
-

The file I've attached has 3 subdirectories, each with a pom in it. I have
re-downloaded the archive attached to this JIRA and it works fine. It is in
tar.gz format, make sure you are downloading the maven-release-issue.tar.gz
file.

release:prepare should support flat directory multi-module projects
---

Attachments: flatProject.main.patch, flatProject.test.patch,
maven-release-issue.tar.gz, MRELEASE-261-with-its-v3.patch,
MRELEASE-261-with-its.patch, MRELEASE-261.patch, PrepareReleaseMojo.patch

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

2009-12-21 Thread Eric Miles (JIRA)


[ 
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203270#action_203270
 ] 

Eric Miles edited comment on MRELEASE-261 at 12/21/09 2:04 PM:
---

I'm not 100% sure this is fixed.  I setup a project to use the beta-10-SNAPSHOT 
plugin and it is still not working, I'm getting the following error while 
trying to prepare the release:

{code}
[INFO] [INFO] 

[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd 
/Users/emiles/Projects/release-workspace/release-parent  svn 
--non-interactive commit --file 
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-1253932520.commit 
--targets 
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-4376558781490229966-targets
[INFO] Working directory: 
/Users/emiles/Projects/release-workspace/release-parent
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{code}

I have confirmed that I am using the beta 10 release as well as I have 
confirmed the beta 10 release in Apache snapshots contained the v3.patch 
identified in one of the previous comments.  I'm attaching my sample project, 
maven-release-issue.tar.gz.  I'm hoping this can be used as a test case and/or 
someone can tell me if I've set the project up incorrectly.

This work is being performed in a Mac OS X environment with JDK 1.5 and SVN 
1.6.6.

An update...I have completely removed the release plugin and am only using the 
svn binary on my box.  I still get the same issue, issuing a similar command
{code}
emiles-macbook:~ emiles$ svn --non-interactive commit --file /tmp/svn-msg 
--targets /tmp/targets 
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{code}

Here's a cat of svn-msg:
{code}
emiles-macbook:~ emiles$ cat /tmp/svn-msg 
[maven-release-plugin] prepare release release-parent-0.0.1emiles-macbook:~ 
emiles$ 
{code}

And a cat of targets:
{code}
emiles$ cat /tmp/targets
/Users/emiles/Projects/release-workspace/release-parent/pom.xml
/Users/emiles/Projects/release-workspace/release-module1/pom.xml
/Users/emiles/Projects/release-workspace/release-module2/pom.xml
{code}

So that this point, I'm beginning to wonder if it's the svn binary causing an 
issue, at this point we have completely circumvented the release plugin.  Or 
maybe it's the way the release plugin is attempting to use SVN?

  was (Author: bigehokie):
I'm not 100% sure this is fixed.  I setup a project to use the 
beta-10-SNAPSHOT plugin and it is still not working, I'm getting the following 
error while trying to prepare the release:

{code}
[INFO] [INFO] 

[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd 
/Users/emiles/Projects/release-workspace/release-parent  svn 
--non-interactive commit --file 
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-1253932520.commit 
--targets 
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-4376558781490229966-targets
[INFO] Working directory: 
/Users/emiles/Projects/release-workspace/release-parent
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{code}

I have confirmed that I am using the beta 10 release as well as I have 
confirmed the beta 10 release in Apache snapshots contained the v3.patch 
identified in one of the previous comments.  I'm attaching my sample project, 
maven-release-issue.tar.gz.  I'm hoping this can be used as a test case and/or 
someone can tell me if I've set the project up incorrectly.

This work is being performed in a Mac OS X environment with JDK 1.5 and SVN 
1.6.6.
  
 release:prepare shouls support flat directory multimodule projects
 --

 Key: MRELEASE-261
 URL: http://jira.codehaus.org/browse/MRELEASE-261
 Project: Maven 2.x Release Plugin
  Issue Type: Improvement
  Components: prepare
 Environment: linux / maven2 / svn
Reporter: paul.whe...@gmail.com
Assignee: Maria Odea Ching
 Fix For: 2.0-beta-10

 Attachments: flatProject.main.patch, flatProject.test.patch, 
 maven-release-issue.tar.gz, MRELEASE-261-with-its-v3.patch,

[jira] Updated: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

2009-12-17 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eric Miles updated MRELEASE-261:

Attachment: maven-release-issue.tar.gz

Sample project that still has release issues in a flat structure

release:prepare shouls support flat directory multimodule projects
--

Attachments: flatProject.main.patch, flatProject.test.patch,
maven-release-issue.tar.gz, MRELEASE-261-with-its-v3.patch,
MRELEASE-261-with-its.patch, MRELEASE-261.patch, PrepareReleaseMojo.patch

[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

2009-12-17 Thread Eric Miles (JIRA)

[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203270#action_203270
]

Eric Miles commented on MRELEASE-261:
-

I'm not 100% sure this is fixed. I setup a project to use the beta-10-SNAPSHOT
plugin and it is still not working, I'm getting the following error while
trying to prepare the release:

{code}
[INFO] [INFO]

[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd
/Users/emiles/Projects/release-workspace/release-parent svn
--non-interactive commit --file
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-1253932520.commit
--targets
/var/folders/fH/fHNZYBGdFd0bMMIPiloA2U+++TI/-Tmp-/maven-scm-4376558781490229966-targets
[INFO] Working directory:
/Users/emiles/Projects/release-workspace/release-parent
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/emiles/Projects/release-workspace' is not a working copy
{code}

I have confirmed that I am using the beta 10 release as well as I have
confirmed the beta 10 release in Apache snapshots contained the v3.patch
identified in one of the previous comments. I'm attaching my sample project,
maven-release-issue.tar.gz. I'm hoping this can be used as a test case and/or
someone can tell me if I've set the project up incorrectly.

This work is being performed in a Mac OS X environment with JDK 1.5 and SVN
1.6.6.

release:prepare shouls support flat directory multimodule projects
--

Attachments: flatProject.main.patch, flatProject.test.patch,
maven-release-issue.tar.gz, MRELEASE-261-with-its-v3.patch,
MRELEASE-261-with-its.patch, MRELEASE-261.patch, PrepareReleaseMojo.patch

[jira] Created: (MEAR-117) Ear resource filtering fails if target destination doesn't exist

2009-11-30 Thread Eric Miles (JIRA)

Ear resource filtering fails if target destination doesn't exist


 Key: MEAR-117
 URL: http://jira.codehaus.org/browse/MEAR-117
 Project: Maven 2.x Ear Plugin
  Issue Type: Bug
Affects Versions: 2.4
 Environment: Windows XP, Maven 2.0.9
Reporter: Eric Miles


In our project structure, we have src/main/application/APP-INF/classes and in 
this folder contains all of our resources.  The desired final outcome is to 
have an ear with APP-INF/classes with the filtered resources.  There are no 
other sources in this ear module so when it is time for the ear plugin to 
filter, we receive an error similar to the following:

Embedded error: 
C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties
 (The system cannot find the path specified)

If I create the 
${project.build.directory}/${project.build.finalName}/APP-INF/classes directory 
on disk before I package, I get no error.  I would think that the resource 
mechanism would be responsible for creating the destination in addition to 
copying/filtering.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (MNG-3191) Filtering not applied to dependency POMs

2007-09-05 Thread Eric Miles (JIRA)

Filtering not applied to dependency POMs


 Key: MNG-3191
 URL: http://jira.codehaus.org/browse/MNG-3191
 Project: Maven 2
  Issue Type: Bug
  Components: Dependencies
Affects Versions: 2.0.7
Reporter: Eric Miles


I have a dependency in my project from a 3rd party, and it's deployed POM has a 
dependency that is determined via filtering.  IE:

dependency
  groupId${repository.database.driver.groupId}/groupId
  artifactId${repository.database.driver.artifactId}/artifactId
  version${repository.database.driver.version}/version
/dependency

When I attempt to reference this dependency in the dependency section of my 
project, I receive the following error while attempting to package:

[DEBUG] Retrieving parent-POM: com.jaspersoft.jasperserver:server::2.0.0
for project:
com.jaspersoft.jasperserver:jasperserver-export-tool-package:jar:2.0.0
from the repository.
[WARNING] POM for
'com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile'
 is invalid. It will be ignored for artifact resolution. Reason: Failed to 
validate POM for project 
com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact 
[com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
[DEBUG] Reason: Failed to validate POM for project
com.jaspersoft.jasperserver:jasperserver-export-tool-package at Artifact
[com.jaspersoft.jasperserver:jasperserver-export-tool-package:pom:2.0.0:compile]
[DEBUG]
Validation Errors:
[DEBUG] 'dependencies.dependency.artifactId' with value
'${repository.database.driver.artifactId}' does not match a valid id
pattern.
[DEBUG] 'dependencies.dependency.groupId' with value
'${repository.database.driver.groupId}' does not match a valid id
pattern.
[DEBUG]


Even if I setup my settings to contain the 3 expression values, they are NOT 
applied to the dependency.  If I check the effective POM for my project, those 
settings are seen so I know I have set it up appropriately.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (CONTINUUM-1359) Installations removed from a profile when Save is clicked.

2007-08-02 Thread Eric Miles (JIRA)

Installations removed from a profile when Save is clicked.


 Key: CONTINUUM-1359
 URL: http://jira.codehaus.org/browse/CONTINUUM-1359
 Project: Continuum
  Issue Type: Bug
  Components: Web - UI
Affects Versions: 1.1-beta-1
Reporter: Eric Miles


If I go into a Profile and add installations then click the Save button near 
the name of the profile, the installations I have added are then removed.  It's 
a little misleading to click Save and to have installations removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SUREFIRE-31) support junit 4.0

2006-12-07 Thread Eric Miles (JIRA)

[ http://jira.codehaus.org/browse/SUREFIRE-31?page=comments#action_82023 ] 

Eric Miles commented on SUREFIRE-31:


I'm able to build and install Karl's 2nd methodhowever, I have no idea how 
to configure maven to use this.  I currently have the snapshot surefire 
installed in my local repositoryhow do I tell maven to use this rather than 
the surefire it's bundled with?  THANKS!

 support junit 4.0
 -

 Key: SUREFIRE-31
 URL: http://jira.codehaus.org/browse/SUREFIRE-31
 Project: surefire
  Issue Type: Improvement
  Components: Junit 4.x support
Reporter: John Didion
 Fix For: 2.1

 Attachments: SUREFIRE-31-maven-surefire-plugin.patch, 
 SUREFIRE-31-surefire-trunk.patch, surefire-junit4.zip, 
 SUREFIRE31_karl_maven-surefire-plugin.patch, 
 SUREFIRE31_karl_surefire_surefire-providers_surefire-junit.patch, 
 SUREFIRE31_karl_surefire_surefire-providers_surefire-junit_2ndMethod.patch


 I know this is a pretty sizable task. I just wanted to get it in the system 
 now that 4.0 has officially been released. Hopefully this will generate some 
 discussion about how 4.0 will be handled - mainly if it will require a 
 completely seperate implemenation of surefire (keeping the same API so it can 
 easily be used by the maven plugin), or if use of 4.0 will be made a 
 configurable option of the current surefire.
 Here's some additional features I'd like to see:
 1. Ability to categorize tests. Unfortunately, 4.0 doesn't include an 
 @Category annotation, or make category a parameter of @Test. However, the 
 filtering mechanism provided by 4.0 is sufficent to support categories given 
 the presense of such an annotation. I recommend putting the @Category 
 annotation in a seperate module (surefire-annotations?) and build support for 
 it into surefire. Hopefully the junit guys could be convinced to incorporate 
 it in a later version.
 2. Similarly, support repeated tests via an @Repeated annotation. I'm not 
 sure how easy this would be to do external to junit.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] (MECLIPSE-441) Packaging type maven-plugin causes unresolved dependencies in multi-module build

[jira] (MDEP-423) Can not unpack dependencies from identified dependent POM without specifying version

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Created: (MRELEASE-516) release:prepare should support a nested/flat hybrid SCM structure

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Updated: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Updated: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Commented: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[jira] Updated: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[jira] Created: (MEAR-117) Ear resource filtering fails if target destination doesn't exist

[jira] Created: (MNG-3191) Filtering not applied to dependency POMs

[jira] Created: (CONTINUUM-1359) Installations removed from a profile when Save is clicked.

[jira] Commented: (SUREFIRE-31) support junit 4.0

25 matches

Site Navigation

Mail list logo

Footer information