[ http://jira.codehaus.org/browse/MEAR-10?page=all ]
Stephane Nicoll reopened MEAR-10:
-
need to set default bundleDir for all ear modules
-
Key: MEAR-10
URL: http
[ http://jira.codehaus.org/browse/MEAR-1?page=all ]
Stephane Nicoll reopened MEAR-1:
Plugin configuration doesn't support .ejb3 and .par EJB modules
---
Key: MEAR-1
URL
[ http://jira.codehaus.org/browse/MEAR-1?page=all ]
Stephane Nicoll closed MEAR-1:
--
Resolution: Fixed
Fix Version: 2.1
Plugin configuration doesn't support .ejb3 and .par EJB modules
(was: Maven)
Key: MANTRUN-13 (was: MNG-998)
Project: Maven 2.x Antrun Plugin (was: Maven 2)
create modules instead of libraries for projects already in the workspace
-
Key: MANTRUN-13
URL
-997)
Project: Maven 2.x Antrun Plugin (was: Maven 2)
create modules for other projects in the reactor
Key: MANTRUN-5
URL: http://jira.codehaus.org/browse/MANTRUN-5
Project: Maven 2.x Antrun Plugin
Type
[ http://jira.codehaus.org/browse/MIDEA-4?page=all ]
Jason van Zyl moved MANTRUN-13 to MIDEA-4:
--
Key: MIDEA-4 (was: MANTRUN-13)
Project: Maven 2.x Idea Plugin (was: Maven 2.x Antrun Plugin)
create modules instead of libraries
[ http://jira.codehaus.org/browse/MIDEA-7?page=all ]
Jason van Zyl moved MANTRUN-5 to MIDEA-7:
-
Key: MIDEA-7 (was: MANTRUN-5)
Project: Maven 2.x Idea Plugin (was: Maven 2.x Antrun Plugin)
create modules for other projects
)
Key: MEAR-1 (was: MNG-1723)
Project: Maven 2.x Ear Plugin (was: Maven 2)
Plugin configuration doesn't support .ejb3 and .par EJB modules
---
Key: MEAR-1
URL: http://jira.codehaus.org/browse/MEAR-1
)
Key: MEAR-14 (was: MNG-954)
Project: Maven 2.x Ear Plugin (was: Maven 2)
Transitive dependencies of War modules should not be copied in the Ear by
default
-
Key: MEAR-14
URL: http
)
Key: MEAR-10 (was: MNG-1488)
Project: Maven 2.x Ear Plugin (was: Maven 2)
need to set default bundleDir for all ear modules
-
Key: MEAR-10
URL: http://jira.codehaus.org/browse/MEAR-10
Project: Maven 2
(was: MNG-1332)
Project: Maven 2.x Eclipse Plugin (was: Maven 2)
Dependent-Modules not showing up in .wtpmodules
---
Key: MECLIPSE-23
URL: http://jira.codehaus.org/browse/MECLIPSE-23
Project: Maven 2.x Eclipse Plugin
-plugin)
Workflow: jira (was: Maven)
Key: MSITE-54 (was: MNG-661)
Project: Maven 2.x Site Plugin (was: Maven 2)
In parent site, automatically create link to modules sites and vice-versa
that has not been 'cooked' and thus
contains uninterpolated expressions (e.g. ${my.var})
we need to use the reactor projects to find the parent as these have been
properly processed.
In parent site, automatically create link to modules sites and vice-versa
[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_53694 ]
Brett Porter commented on MNG-661:
--
John - please create a new issue for your staging site problems
In parent site, automatically create link to modules sites and vice-versa
[ http://jira.codehaus.org/browse/MNG-1181?page=all ]
Brett Porter updated MNG-1181:
--
Fix Version: (was: 2.0.1)
2.0.2
MavenEmbedder.execute() doesn't run reactor modules
[ http://jira.codehaus.org/browse/MNG-1760?page=all ]
Brett Porter reopened MNG-1760:
---
Custom packaging type ignored when POM contains modules entry
--
Key: MNG-1760
URL
[ http://jira.codehaus.org/browse/MNG-1760?page=all ]
Brett Porter closed MNG-1760:
-
Assign To: Brett Porter
Resolution: Won't Fix
Custom packaging type ignored when POM contains modules entry
a project with sub modules without adding all
the sub modules
--
Key: CONTINUUM-501
URL: http://jira.codehaus.org/browse/CONTINUUM-501
Project: Continuum
Type: Improvement
) );
}
baseDir = buffer.toString() ;
System.out.println( new baseDir = + baseDir );
}
if ( baseDir.startsWith( / ) )
{
return repository.getHost() + baseDir;
}
In parent site, automatically create link to modules sites and vice-versa
It should be possible to add a project with sub modules without adding all the
sub modules
--
Key: CONTINUUM-501
URL: http://jira.codehaus.org/browse/CONTINUUM-501
Project: Continuum
mvn install - multiple modules using subproject as launch point - pom.xml gets
renamed installed in local repository as a .war file
---
Key: MNG-1784
[ http://jira.codehaus.org/browse/CONTINUUM-501?page=comments#action_53080
]
Dan Tran commented on CONTINUUM-501:
Continuum site suggests to use a wrapper batch script and create a shell project
It should be possible to add a project with sub modules
changes to default to the getModulesMenu() and
getProjectParentMenu()
reporting output directory for if the parent\child urls are not set.
If you would like the changes I can upload a diff of the changes
Patrick
In parent site, automatically create link to modules sites and vice-versa
this is a programmed
limitation and not a bug
Custom packaging type ignored when POM contains modules entry
--
Key: MNG-1760
URL: http://jira.codehaus.org/browse/MNG-1760
Project: Maven 2
Type: Bug
Custom packaging type ignored when POM contains modules entry
--
Key: MNG-1760
URL: http://jira.codehaus.org/browse/MNG-1760
Project: Maven 2
Type: Bug
Reporter: Aaron Anderson
First I have not come
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
Vincent Siveton closed MNG-661:
---
Resolution: Fixed
Applied. Thanks John!
In parent site, automatically create link to modules sites and vice-versa
[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52746 ]
John Allen commented on MNG-661:
Vincent, the patch seems to be missing the new SiteStage mojo.
In parent site, automatically create link to modules sites and vice-versa
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
Vincent Siveton updated MNG-661:
Attachment: MNG-661.diff
Repost with SiteStageMojo
In parent site, automatically create link to modules sites and vice-versa
an internally published site).
In parent site, automatically create link to modules sites and vice-versa
-
Key: MNG-661
URL: http://jira.codehaus.org/browse/MNG-661
Project: Maven 2
Type
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
John Casey updated MNG-661:
---
Fix Version: (was: 2.0.1)
2.0.2
In parent site, automatically create link to modules sites and vice-versa
* stagingSiteURL could be scp://www.mycompany.com/www/project/ (ie samething
that the distributionManagement.site.url element)
I will put a new diff file with your proposal and a dummy project.
BTW, this issue could be related to MNG-983
In parent site, automatically create link to modules
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
Vincent Siveton updated MNG-661:
Attachment: site-plugin-multiproject.zip
MNG-661.diff
diff file and dummy project
In parent site, automatically create link to modules sites and vice
simulate? I know to
us its simulating the real site deployment but in terms of business process the
user is staging it for testing or local review. Not gonna get religous over
about it though :)
In parent site, automatically create link to modules sites and vice-versa
Plugin configuration doesn't support .ejb3 and .par EJB modules
---
Key: MPEAR-43
URL: http://jira.codehaus.org/browse/MPEAR-43
Project: maven-ear-plugin
Type: Bug
Reporter: Tim Kettler
Priority
-plugin)
Plugin configuration doesn't support .ejb3 and .par EJB modules
---
Key: MNG-1723
URL: http://jira.codehaus.org/browse/MNG-1723
Project: Maven 2
Type: Bug
Reporter: Tim Kettler
Priority
[ http://jira.codehaus.org/browse/MNG-1723?page=all ]
Stephane Nicoll updated MNG-1723:
-
Version: 2.0
Component: maven-ear-plugin
Plugin configuration doesn't support .ejb3 and .par EJB modules
modules
---
Key: MNG-1723
URL: http://jira.codehaus.org/browse/MNG-1723
Project: Maven 2
Type: Bug
Components: maven-ear-plugin
Versions: 2.0
Reporter: Tim Kettler
Assignee: Stephane
[ http://jira.codehaus.org/browse/MNG-1723?page=all ]
Stephane Nicoll closed MNG-1723:
Resolution: Fixed
Fix Version: 2.0.1
Got access to SVN finally. Applied and fixed.
Plugin configuration doesn't support .ejb3 and .par EJB modules
to use the project.url.
The Mojo will create the following structure and all links (parent project and
modules) should be hardcode.
C:\testingsite
|-myHost
|-www
|--myPath
|--multiproject
|--framework1
|-myOtherHost
|-www
|--myOtherPath
|--framework2
work until the site(s) are deployed but I felt constrained to comply by
the maven project model for what defines a projects 'home' and how it relates
to its partent, child modules and its distribution management details.
My observations:-
* A project can (and therefore someone will) define its
[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_51842 ]
Gopal Patwa commented on MNG-661:
-
I am using this type of relative url link for all sub modules in staging, so it
can work with parent site and it works
url../../module-name
links and module
links.
But, the code uses project.getParent().getUrl() to find the path (if I don't
miss something). So, we need to deploy on a web server all projects (before
testing for instance).
IMHO, I think it could be best to copy all generated sites (I mean modules
site) in the parent
[ http://jira.codehaus.org/browse/MNG-1619?page=all ]
Brett Porter closed MNG-1619:
-
Assign To: Brett Porter
Resolution: Won't Fix
this layout wasn't supported, and the error is cleared up in 2.0.1 (packaging
JAR cannot have modules).
The module
[ http://jira.codehaus.org/browse/MNG-1620?page=all ]
Brett Porter updated MNG-1620:
--
Version: (was: 2.1)
2.0
par and ejb3 files must expose its classes to the classpath, so other modules
can use them when compiling
[ http://jira.codehaus.org/browse/MNG-1620?page=all ]
Brett Porter closed MNG-1620:
-
Assign To: Brett Porter
Resolution: Fixed
Fix Version: 2.0.1
applied, thanks
par and ejb3 files must expose its classes to the classpath, so other modules
bug using modules/ in a flat layout
-
Key: MNG-1619
URL: http://jira.codehaus.org/browse/MNG-1619
Project: Maven 2
Type: Bug
Versions: 2.0
Reporter: Wim Deblauwe
Attachments: modules.zip
I have a problem using
par and ejb3 files must expose its classes to the classpath, so other modules
can use them when compiling
-
Key: MNG-1620
URL: http://jira.codehaus.org/browse/MNG-1620
[ http://jira.codehaus.org/browse/MNG-1181?page=all ]
John Casey updated MNG-1181:
Description:
MavenEmbedder.execute() doesn't run reactor modules.
I've been trying to run it with generate-sources goal, but it only build the
root project
a bundleDir entry, this value is
taken. Mike, if you have modified something useful, feel free to send a patch.
need to set default bundleDir for all ear modules
-
Key: MNG-1488
URL: http://jira.codehaus.org/browse/MNG-1488
there. If a javamodule has a bundleDir entry, this value is
taken.
need to set default bundleDir for all ear modules
-
Key: MNG-1488
URL: http://jira.codehaus.org/browse/MNG-1488
Project: Maven 2
Type: New Feature
[ http://jira.codehaus.org/browse/MNG-1488?page=comments#action_50756 ]
Stephane Nicoll commented on MNG-1488:
--
Mmm. Are you sure you want to apply this for *all* modules.
It would make more sense to put 3rd party libraries (utilites co) in
APP-INF
[ http://jira.codehaus.org/browse/MNG-1488?page=comments#action_50779 ]
mike perham commented on MNG-1488:
--
+1 I have this same need. All 3rd party jars should go in lib/ while the app
modules should stay in the EAR root. I modified the ear plugin to do
in Add
Project page
I fixed continuum for support multiproject with your directories tree, so
you'll can use module with ../ in module name in next version, only if you have
the correct directory structure on site you access with protocol
Maven 2 parent project with modules/ cannot be build
need to set default bundleDir for all ear modules
-
Key: MNG-1488
URL: http://jira.codehaus.org/browse/MNG-1488
Project: Maven 2
Type: New Feature
Components: maven-ear-plugin
Reporter: Michal Stochmialek
I
.
In parent site, automatically create link to modules sites and vice-versa
-
Key: MNG-661
URL: http://jira.codehaus.org/browse/MNG-661
Project: Maven 2
Type: Improvement
Components: maven-site
Maven 2 parent project with modules/ cannot be build if parent is on same
level as modules
Key: CONTINUUM-437
URL: http://jira.codehaus.org/browse/CONTINUUM-437
Project: Continuum
Support in multiproject environment modules with different named POMs
-
Key: MNG-1493
URL: http://jira.codehaus.org/browse/MNG-1493
Project: Maven 2
Type: Improvement
Components: maven-model
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
John Allen updated MNG-661:
---
Attachment: SiteMojoPatch.txt
Patch reinstates modules support through use of reactor projects and the
parsing of their distributionManagement site information.
In parent
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
John Allen updated MNG-661:
---
Attachment: SiteMojoPatch.txt
My bad, missed bug for leaf nodes that resulted in empty modules menu. New
patch has one line difference to previous patch, namely line 791
Explain that uploading a POM file works only for a single project without
modules
-
Key: CONTINUUM-425
URL: http://jira.codehaus.org/browse/CONTINUUM-425
Project: Continuum
Type
[ http://jira.codehaus.org/browse/MNG-997?page=comments#action_50262 ]
John Casey commented on MNG-997:
Brett,
What's this about? Is it pending still?
create modules for other projects in the reactor
was loaded into the workspace, however
I think we now sync the workspace modules list with the project modules list
create modules for other projects in the reactor
Key: MNG-997
URL: http://jira.codehaus.org/browse/MNG-997
project without
modules
-
Key: CONTINUUM-425
URL: http://jira.codehaus.org/browse/CONTINUUM-425
Project: Continuum
Type: Improvement
Components: continuum-web
Versions: 1.0
[ http://jira.codehaus.org/browse/MNG-998?page=all ]
Brett Porter closed MNG-998:
Assign To: Brett Porter (was: Johnny R. Ruiz III)
Resolution: Fixed
I redid this using ${reactorProjects}
create modules instead of libraries for projects already
Possibility to aggrates sources from other modules
--
Key: MNG-1406
URL: http://jira.codehaus.org/browse/MNG-1406
Project: Maven 2
Type: New Feature
Components: maven-assembly-plugin
Reporter: Alexandre Poitras
in their
configuration and then running assembly:assembly goal on the parent project
would aggregate all this fragments in one archive. It would solve all the
issues raised about multiprojects aggregation right now. Just my two cents.
Possibility to aggrates sources from other modules
[ http://jira.codehaus.org/browse/MNG-764?page=all ]
Brett Porter closed MNG-764:
Resolution: Fixed
applied, thanks. Note that if we later allow other packagings to aggregate,
this will need to take it into account
pom with modules should fail
[ http://jira.codehaus.org/browse/MNG-1332?page=all ]
fabrizio giustina closed MNG-1332:
--
Assign To: fabrizio giustina
Resolution: Fixed
fixed in svn for 2.0-beta-3, thanks
Dependent-Modules not showing up in .wtpmodules
Dependent-Modules not showing up in .wtpmodules
---
Key: MNG-1332
URL: http://jira.codehaus.org/browse/MNG-1332
Project: Maven 2
Type: Bug
Components: maven-eclipse-plugin
Versions: 2.0
Environment: jsdk
Validation Messages:
[0] packaging 'war' is invalid. Aggregator projects require 'pom' as
packaging.
Reason: Failed to validate POM
[INFO]
pom with modules should fail if packaging is not pom or an aggregator
.
What I did is get all modules of the parent and check each dependency if it
is already in the module list.
- I cannot use the value of getCollectedProjects() since when plugin is
executing in the modules, getParent.getCollectedProjects() returns null.
- I cannot read the module line
[ http://jira.codehaus.org/browse/MNG-1223?page=all ]
Brett Porter closed MNG-1223:
-
Assign To: Brett Porter
Resolution: Fixed
Fix Version: 2.0.1
warning with multiple child modules with the same artifact id
warning with multiple child modules with the same artifact id
-
Key: MNG-1223
URL: http://jira.codehaus.org/browse/MNG-1223
Project: Maven 2
Type: New Feature
Reporter: Matthew Pocock
Priority: Minor
MavenEmbedder.execute() doesn't run reactor modules
---
Key: MNG-1181
URL: http://jira.codehaus.org/browse/MNG-1181
Project: Maven 2
Type: Bug
Components: maven-embedder
Reporter: Eugene Kuleshov
Priority
Hi,
I know this is not slated for Maven 2.0 but I'd like to start a discussion
about how to share common build files between modules.
Example of use cases:
- sharing a checkstyle.xml file
- sharing a LICENSE file
- sharing PMD, findbugs, etc config files
- etc
We don't want to use relative
a discussion
about how to share common build files between modules.
Example of use cases:
- sharing a checkstyle.xml file
- sharing a LICENSE file
- sharing PMD, findbugs, etc config files
- etc
We don't want to use relative paths as each module should be able to be
built independently of the rest with only
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: jeudi 6 octobre 2005 14:00
To: Maven Developers List
Subject: Re: [Design] Sharing common build files between modules
It isn't necessary to put them in repository, but they need only to be
accessible
sure. and we'll can versionned them
Emmanuel
Vincent Massol a écrit :
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: jeudi 6 octobre 2005 14:00
To: Maven Developers List
Subject: Re: [Design] Sharing common build files between modules
It isn't necessary
[ http://jira.codehaus.org/browse/MNG-764?page=all ]
Brett Porter updated MNG-764:
-
Fix Version: (was: 2.0-beta-3)
2.0.1
pom with modules should fail if packaging is not pom or an aggregator
Transitive dependencies of War modules should not be copied in the Ear by
default
-
Key: MNG-954
URL: http://jira.codehaus.org/browse/MNG-954
Project: Maven 2
Type: Improvement
[ http://jira.codehaus.org/browse/MNG-954?page=all ]
Brett Porter closed MNG-954:
Assign To: Brett Porter
Resolution: Duplicate
Transitive dependencies of War modules should not be copied in the Ear by
default
[ http://jira.codehaus.org/browse/MNG-764?page=all ]
Brett Porter updated MNG-764:
-
Component: maven-core
pom with modules should fail if packaging is not pom or an aggregator
create modules for other projects in the reactor
Key: MNG-997
URL: http://jira.codehaus.org/browse/MNG-997
Project: Maven 2
Type: Improvement
Components: maven-idea-plugin
Reporter: Brett Porter
Fix For: 2.0
create modules instead of libraries for projects already in the workspace
-
Key: MNG-998
URL: http://jira.codehaus.org/browse/MNG-998
Project: Maven 2
Type: Improvement
Components: maven-idea
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
Brett Porter updated MNG-661:
-
Component: (was: maven-plugins)
maven-site-plugin
In parent site, automatically create link to modules sites and vice-versa
Please upload missing XDoclet 1.2.3 modules
---
Key: MAVENUPLOAD-512
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-512
Project: maven-upload-requests
Type: Task
Reporter: Markus Wiederkehr
https://sup.xicrypt.com/pub
[
http://jira.codehaus.org/browse/MAVENUPLOAD-512?page=comments#action_46195 ]
Carlos Sanchez commented on MAVENUPLOAD-512:
Please post all the urls.
Please upload missing XDoclet 1.2.3 modules
-bundle.jar
https://sup.xicrypt.com/pub/xdoclet-tjdo-module-1.2.3-bundle.jar
https://sup.xicrypt.com/pub/xdoclet-webwork-module-1.2.3-bundle.jar
https://sup.xicrypt.com/pub/xdoclet-wsee-module-1.2.3-bundle.jar
Please upload missing XDoclet 1.2.3 modules
[ http://jira.codehaus.org/browse/MAVENUPLOAD-512?page=all ]
Carlos Sanchez closed MAVENUPLOAD-512:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Please upload missing XDoclet 1.2.3 modules
and has been removed
- Added includeInApplicationXml property on JavaModule to allow it to be
included in the generated application.xml
Add a property to exclude all java modules ('jar') from application.xml
generation
also to handle jar
modules which needs to be declared in a
module
java[...]/java
/module
entry.
Summary: Add a property to exclude all java modules ('jar') from
application.xml generation (was: Improve the declaration of 3rd party library
and exclusion)
Add a property to exclude all
specific behavior.
okay?
Add a property to exclude all java modules ('jar') from application.xml
generation
--
Key: MNG-826
URL: http://jira.codehaus.org/browse/MNG-826
Project: Maven 2
a property to exclude all java modules ('jar') from application.xml
generation
--
Key: MNG-826
URL: http://jira.codehaus.org/browse/MNG-826
Project: Maven 2
Type: Improvement
[ http://jira.codehaus.org/browse/MNG-661?page=all ]
Brett Porter updated MNG-661:
-
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
In parent site, automatically create link to modules sites and vice-versa
doesn't link the modules
--
Key: MPIDEA-30
URL: http://jira.codehaus.org/browse/MPIDEA-30
Project: maven-idea-plugin
Type: Improvement
Versions: 1.6, 1.5
Reporter: Graham Triggs
[ http://jira.codehaus.org/browse/MPIDEA-30?page=all ]
Graham Triggs updated MPIDEA-30:
Attachment: module.jelly
Updated the module creation, so that when you link dependencies to the JARs in
the repository instead of other modules, it generates
directories to JAR
dependencies that relate to modules in the reactor.
Allow multiproject processing that optionally doesn't link the modules
--
Key: MPIDEA-30
URL: http://jira.codehaus.org/browse/MPIDEA-30
link the modules
--
Key: MPIDEA-30
URL: http://jira.codehaus.org/browse/MPIDEA-30
Project: maven-idea-plugin
Type: Improvement
Versions: 1.6, 1.5
Reporter: Graham Triggs
Priority
know if there is a problem.
Allow multiproject processing that optionally doesn't link the modules
--
Key: MPIDEA-30
URL: http://jira.codehaus.org/browse/MPIDEA-30
Project: maven-idea-plugin
Allow multiproject processing that optionally doesn't link the modules
--
Key: MPIDEA-30
URL: http://jira.codehaus.org/browse/MPIDEA-30
Project: maven-idea-plugin
Type: Improvement
Versions
301 - 400 of 459 matches
Mail list logo
