wsdl4j-qname
Key: MAVENUPLOAD-582
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-582
Project: maven-upload-requests
Type: Sub-task
Reporter: Joerg Schaible
Found the "create sub-task" functionality now ... :)
--
This message is automatically ge
[ http://jira.codehaus.org/browse/MNG-1104?page=all ]
John Tolentino updated MNG-1104:
Attachment: MNG-1104-maven-release-plugin.patch
Added filter in getStatus() method.
> release plugin should ignore pom.xml from status check
> ---
[ http://jira.codehaus.org/browse/MAVENUPLOAD-580?page=all ]
Joerg Schaible reopened MAVENUPLOAD-580:
Hi Carlos, you forgot the second bundle. I remember, that I saw a comment of
you to add additional bundles in the same JIRA issue instead of o
[ http://jira.codehaus.org/browse/MNG-1355?page=comments#action_50280 ]
Edwin Punzalan commented on MNG-1355:
-
Hi, the cause of the infinite loop is not the depth of the project and/or the
modules in it.
Look in the ui-toolkit/subproject/swing/pom.xml a
[ http://jira.codehaus.org/browse/MNG-1430?page=comments#action_50279 ]
Dietrich Schulten commented on MNG-1430:
Not sure. Can we assume that everybody wants the wtp builders and natures for
war? There are other web application plugins. Besides we wo
[ http://jira.codehaus.org/browse/MNG-1394?page=all ]
Edwin Punzalan updated MNG-1394:
Attachment: MNG-1394-maven-project.patch
Please see attached patch.
> Use of the RelativePath Multi-Module produces failure
>
[ http://jira.codehaus.org/browse/MEV-183?page=all ]
Edwin Punzalan closed MEV-183:
--
Assign To: Edwin Punzalan
Resolution: Fixed
> Move common-test to its correct directory
> -
>
> Key: MEV-183
>
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50276 ]
Vincent Massol commented on MNG-1356:
-
Hi John,
Yes, it's Cargo which is downloading the container distribution.
Using a plugin configuration is exactly what I'm after but it wasn't
[ http://jira.codehaus.org/browse/MNG-1452?page=comments#action_50275 ]
Jason van Zyl commented on MNG-1452:
We are going to have to do some legwork at the front-end or at the back-end. I
think making a POM that actually represents what's in the JAR is a
[ http://jira.codehaus.org/browse/MEV-189?page=all ]
Edwin Punzalan closed MEV-189:
--
Resolution: Fixed
Fixed
> saaj pom wrong?
> ---
>
> Key: MEV-189
> URL: http://jira.codehaus.org/browse/MEV-189
> Project: Maven Ev
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/08-Nov-2005_12.30.21/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
[ http://jira.codehaus.org/browse/MEV-188?page=all ]
Carlos Sanchez closed MEV-188:
--
Resolution: Fixed
> Relocate tonic and jarjar groupIds to com.tonicsystems
> --
>
> Key: MEV-188
>
[ http://jira.codehaus.org/browse/MEV-177?page=all ]
Tomislav Stojcevich closed MEV-177:
---
Resolution: Fixed
> older jstl jars in old location need relocation tag added
> -
>
> Key: M
[ http://jira.codehaus.org/browse/MEV-177?page=comments#action_50272 ]
Tomislav Stojcevich commented on MEV-177:
-
It seems to be ok now. The old version must have been cached somewhere or the
mirrors had sync issue or something.
> older jstl jars i
[ http://jira.codehaus.org/browse/MNG-1104?page=comments#action_50271 ]
John Casey commented on MNG-1104:
-
I suppose the next step is always to commit the pom.xml with the new
before tagging, so it's not that big of a deal...
> release plugin should ignore
[ http://jira.codehaus.org/browse/MNG-1104?page=comments#action_50269 ]
John Casey commented on MNG-1104:
-
is this so you don't have to commit when you've just changed a dependency
version away from a -SNAPSHOT?
> release plugin should ignore pom.xml from s
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50268 ]
John Casey commented on MNG-1323:
-
It looks like some of the work I did to get the ant-mojo support up and running
was related to this. Kenney's 04/Nov/2005 post was related to my fix fo
Exception error messages and i18n
-
Key: MNG-1453
URL: http://jira.codehaus.org/browse/MNG-1453
Project: Maven 2
Type: Improvement
Components: maven-core
Versions: 2.0
Environment: all
Reporter: Corridor Software Devel
[ http://jira.codehaus.org/browse/MNG-997?page=all ]
Brett Porter closed MNG-997:
Assign To: Brett Porter
Resolution: Duplicate
Fix Version: (was: 2.0.1)
mng-998 actually implemented this.
998 was meant to be for when the module was load
[ 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
>
>
>
[ http://jira.codehaus.org/browse/MNG-1130?page=all ]
Brett Porter reopened MNG-1130:
---
forgot to apply jar-sign-verify.diff. needs to be updated to apply.
> Support jar signing.
>
>
> Key: MNG-1130
> URL: http://jir
[ http://jira.codehaus.org/browse/MNG-1379?page=comments#action_50260 ]
John Casey commented on MNG-1379:
-
I just tested this with a (somewhat) out-of-date 2.0-beta-3-SNAPSHOT build of
the maven-eclipse-plugin, and from what I could tell of the .classpath fi
[ http://jira.codehaus.org/browse/MNG-1379?page=comments#action_50258 ]
John Casey commented on MNG-1379:
-
is this a problem with the eclipse plugin??
> Wrong path for artifacts with system scope
> --
>
> Key:
[ http://jira.codehaus.org/browse/MNG-1388?page=comments#action_50257 ]
John Casey commented on MNG-1388:
-
This happens because dependency POMs aren't currently candidates for profile
triggering.
However, it seems we will have to trigger profiles for these
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50256 ]
John Casey commented on MNG-1356:
-
Alternately, if your plugin is downloading the containers, can't you simply use
a plugin configuration that specifies ${java.io.tmp.dir} as the value?
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50255 ]
John Casey commented on MNG-1356:
-
are these containers artifacts that could be resolved as part of a
plugin-dependency? That is to say, could you do:
cargo-maven-
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/07-Nov-2005_08.30.33/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
[ http://jira.codehaus.org/browse/MEV-177?page=comments#action_50254 ]
Edwin Punzalan commented on MEV-177:
Something must have gone wrong during the update of 1.0.2... In our copies in
SVN, 1.0.2 has the relocation.
Maybe Carlos can shed some light int
[ http://jira.codehaus.org/browse/MEV-169?page=all ]
Edwin Punzalan closed MEV-169:
--
Resolution: Fixed
I see them now... Yesterday when I looked, its not there yet.
I'm closing this issue now.
> Relocated dependency for tagsoup in xom
> -
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20051108.001500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20051108.001500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
[ http://jira.codehaus.org/browse/MEV-189?page=all ]
Carlos Sanchez moved MRM-24 to MEV-189:
---
Priority: (was: Minor)
Key: MEV-189 (was: MRM-24)
Project: Maven Evangelism (was: Maven Repository Manager)
> saaj pom wrong?
> --
Relocate tonic and jarjar groupIds to com.tonicsystems
--
Key: MEV-188
URL: http://jira.codehaus.org/browse/MEV-188
Project: Maven Evangelism
Type: Improvement
Reporter: Carlos Sanchez
Assigned to: Edwin Punzal
[ http://jira.codehaus.org/browse/CONTINUUM-378?page=comments#action_50252
]
Emmanuel Venisse commented on CONTINUUM-378:
I'll check if schedule deleted in database are stopped too. If it's the pb, you
need to resynchronize schedules and databas
saaj pom wrong?
---
Key: MRM-24
URL: http://jira.codehaus.org/browse/MRM-24
Project: Maven Repository Manager
Type: Bug
Reporter: Robert Egglestone
Priority: Minor
The saaj pom contains the details for jaxm rather than saaj:
http://www.ibiblio.o
[ http://jira.codehaus.org/browse/CONTINUUM-378?page=comments#action_50251
]
Scott Schram commented on CONTINUUM-378:
They are all set to the default group and DEFAULT_SCHEDULE.
I did change them, experimenting with the program, then changed them ba
[ http://jira.codehaus.org/browse/CONTINUUM-367?page=all ]
Emmanuel Venisse closed CONTINUUM-367:
--
Resolution: Fixed
Fixed. We certainly need to do more work on continuum-xml-rpc, but this issue
is fixed.
> error when calling getprojects() th
Thanks.
On 11/5/05, Phil Steitz <[EMAIL PROTECTED]> wrote:
> Carlos Sanchez wrote:
> > Hi,
> >
> > Some days ago I created a patch to fix a lot of commons poms. If
> > somebody with enough karma could try to push this through...
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=37314
>
> W
[ http://jira.codehaus.org/browse/MNG-1247?page=comments#action_50249 ]
Julien Dubois commented on MNG-1247:
Even if it's the Manifest parser's fault, this should at least be documented
clearly in the POM documentation.
I've got the same problem on Mac
Hi,
I suggest you to create two repos (snapshots and releases) under the
cargo project. When the sync program is available it's just a matter
of rsync the releases repo to ibiblio. In the meantime you can add it
to the pom and be able to build. Just remember to use fully qualified
groupIds (org.co
[ http://jira.codehaus.org/browse/MNG-1310?page=comments#action_50248 ]
Jerome Lacoste commented on MNG-1310:
-
MNG-1251 was checked in, but my patch not taken in. In particular, the
overloaded attachArtifact() method has not been made visible from the
M
[ http://jira.codehaus.org/browse/MNG-1452?page=comments#action_50247 ]
Brett Porter commented on MNG-1452:
---
if this is done with a classifier or just a change in extension, then it would
complicate the system to create a new POM.
Is anything in the POM c
best practices: deployment of aggregate JARs produced by the assembly plug-in
-
Key: MNG-1452
URL: http://jira.codehaus.org/browse/MNG-1452
Project: Maven 2
Type: Task
Components: best prac
[ http://jira.codehaus.org/browse/MNG-699?page=comments#action_50245 ]
Brett Porter commented on MNG-699:
--
it's up to you. If you think the mojo versions are better, take those - or
combine the two.
I just think the final destination should be the Apache M
[ http://jira.codehaus.org/browse/MNG-1449?page=all ]
Brett Porter closed MNG-1449:
-
Assign To: Brett Porter
Resolution: Won't Fix
that's not a bug. It's valid to have a jar with no sources (eg, just resources).
IT does print a warning
> Maven cr
Fixed.
I also removed the extra "surefire" directory in that repository as it
was inconsistent with all the others. So you can check it out with:
svn co https://svn.apache.org/repos/asf/maven/surefire/trunk surefire
- Brett
Emmanuel Venisse wrote:
Thanks Jason.
Jason van Zyl a écrit :
Hi
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50240 ]
Carlos Sanchez commented on MAVENUPLOAD-578:
If they wanna go with com.ibm.as400 then a web page at ibm.com saying that the
project is hosted there and called as400 o
Hi,
On 11/7/05, Brett Porter (JIRA) <[EMAIL PROTECTED]> wrote:
> we won't be allowing maven-model-2.0-all into the plugin, its v4 classes will
> conflict with the root classloader.
> What is needed is a way to get maven-model-3.0.1 into the plugin, really.
> That may be best done by changing the
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/07-Nov-2005_04.30.40/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50236 ]
Brian Bonner commented on MAVENUPLOAD-578:
--
I'm asking Jeff Lee (on the project team) what his thought are. Since it's
open sourced, I'm going to guess they go for net.
[ http://jira.codehaus.org/browse/MEV-187?page=comments#action_50233 ]
Jeff Genender commented on MEV-187:
---
Whoops...that link i gave for our personal repo is on codehaus.
> ActiveMQ 3.2 POM is invalid (contains variable refs based on maven 1)
> --
[ http://jira.codehaus.org/browse/MEV-187?page=comments#action_50232 ]
Jeff Genender commented on MEV-187:
---
Based on this being in ibiblio and you are the gate keepers (per Brett) this
should never have gotten into ibiblio in the first place. IMHO, you ca
My fault, I added before the properties without the "svn:"
On 11/6/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> >
> > Propchange:
> > maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt
> > ('eol-style' removed)
> >
> > Propchange:
> > maven/site/trunk/src/site/ap
[ http://jira.codehaus.org/browse/MEV-186?page=comments#action_50231 ]
Carlos Sanchez commented on MEV-186:
Read MEV-177
> displaytag has wrong dependency for jstl
>
>
> Key: MEV-186
> URL: http:
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50230 ]
Carlos Sanchez commented on MAVENUPLOAD-578:
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
<>
we need proof of control, or use net.sf.jt400 as groupId
[ http://jira.codehaus.org/browse/MEV-187?page=comments#action_50229 ]
Carlos Sanchez commented on MEV-187:
we can fix the pom.currentVersion, but what can we do with the other versions?
this needs to be reported to activemq guys
> ActiveMQ 3.2 POM is i
[ http://jira.codehaus.org/browse/MEV-186?page=comments#action_50228 ]
Oliver Siegmar commented on MEV-186:
I don't know what a relocation pom is, but in one of my projects jstl 1.0.2 and
1.1.2 get both included, because one is from groupId javax.servlet
[ http://jira.codehaus.org/browse/MEV-186?page=comments#action_50227 ]
Carlos Sanchez commented on MEV-186:
But there's a relocation pom, this should'n be needed at all and we don't want
to start changing all the poms when another is moved from place
>
[ http://jira.codehaus.org/browse/MEV-186?page=all ]
Carlos Sanchez closed MEV-186:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
> displaytag has wrong dependency for jstl
>
>
> Key: MEV-186
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50226 ]
Brian Bonner commented on MAVENUPLOAD-578:
--
Code is open sourced by IBM. What is the groupid based upon? It's hosted on
sourceforge project, but all packages on code
[ http://jira.codehaus.org/browse/MEV-179?page=all ]
Carlos Sanchez closed MEV-179:
--
Assign To: Carlos Sanchez
Resolution: Won't Fix
> Axis 1.2.1 WSDL4J dependency points to wrong place
> --
>
>
[ http://jira.codehaus.org/browse/MAVENUPLOAD-530?page=all ]
Carlos Sanchez closed MAVENUPLOAD-530:
--
Assign To: Carlos Sanchez
Resolution: Incomplete
> JCommon RC1 upload
> --
>
> Key: MAVENUPLOAD-530
> UR
[ http://jira.codehaus.org/browse/MAVENUPLOAD-533?page=all ]
Carlos Sanchez closed MAVENUPLOAD-533:
--
Assign To: Carlos Sanchez
Resolution: Incomplete
> Upload XOM 1.1b4 to maven
> -
>
> Key: MAVENUPLOAD-533
[ http://jira.codehaus.org/browse/MAVENUPLOAD-581?page=all ]
Carlos Sanchez closed MAVENUPLOAD-581:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Upload wicket-1.1-bundle.jar and wicket-extensions-1.1-bundle.jar
>
[ http://jira.codehaus.org/browse/MAVENUPLOAD-580?page=all ]
Carlos Sanchez closed MAVENUPLOAD-580:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Upload wsdl4j 1.5.1
> ---
>
> Key: MAVENUPLOAD-580
> URL:
[ http://jira.codehaus.org/browse/MAVENUPLOAD-569?page=all ]
Carlos Sanchez closed MAVENUPLOAD-569:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Copied everything by hand
You may want to move the plugin to maven-plugins.sf.net, we'll setup
[
http://jira.codehaus.org/browse/MAVENUPLOAD-578?page=comments#action_50224 ]
Carlos Sanchez commented on MAVENUPLOAD-578:
groupId is not rigth, there's no proof of controlling com.ibm.as400
> jt400-4.8.0-bundle
> --
>
>
[ http://jira.codehaus.org/browse/MEV-185?page=comments#action_50223 ]
Carlos Sanchez commented on MEV-185:
Why optional has to be true ?
> commons-logging-1.0.4 POM dependencies not using properly
> -
[ http://jira.codehaus.org/browse/MEV-187?page=all ]
Carlos Sanchez moved MNG-1451 to MEV-187:
-
Priority: (was: Critical)
Group ID: activemq
Version: (was: 2.0)
Artifact ID: activemq
Version: 3.2
Complexi
ok, digging this old thing out the dust bin..
I have abandoned my old layout (and the current structure provided by the
j2ee archetype) and shifting towards something that is more like the current
state of the maven repo...and I am trying to decide the lvl of nesting that
is useful for the compone
Failing when the version is missing should be optional
--
Key: MPANNOUNCEMENT-19
URL: http://jira.codehaus.org/browse/MPANNOUNCEMENT-19
Project: maven-announcement-plugin
Type: Improvement
Versions: 1.3
[ http://jira.codehaus.org/browse/SCM-69?page=comments#action_50221 ]
Emmanuel Venisse commented on SCM-69:
-
It's a svn message. We can't know in maven scm what it the cause of it.
> Improve error message when commit over https fails
> --
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051107.183001.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051107.183001.txt
Upload wicket-1.1-bundle.jar and wicket-extensions-1.1-bundle.jar
-
Key: MAVENUPLOAD-581
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-581
Project: maven-upload-requests
Type: Task
Reporter: Marti
[ http://jira.codehaus.org/browse/MEV-186?page=all ]
Oliver Siegmar updated MEV-186:
---
Attachment: displaytag-jstl.diff
Here's a fix
> displaytag has wrong dependency for jstl
>
>
> Key: MEV-186
>
displaytag has wrong dependency for jstl
Key: MEV-186
URL: http://jira.codehaus.org/browse/MEV-186
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Reporter: Oliver Siegmar
The groupId for jstl should be j
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051107.173000.tar.gz
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051107.173000.txt
[ http://jira.codehaus.org/browse/MNG-1451?page=comments#action_50217 ]
Jeff Genender commented on MNG-1451:
Probably should have added this is in the m2 repo on ibiblio.
> ActiveMQ 3.2 POM is invalid (contains variable refs based on maven 1)
> -
ActiveMQ 3.2 POM is invalid (contains variable refs based on maven 1)
-
Key: MNG-1451
URL: http://jira.codehaus.org/browse/MNG-1451
Project: Maven 2
Type: Bug
Versions: 2.0
Reporter: Jeff
But the user
being able to file correctly in the first place is probably more
important.
I agree. I'm just wondering then why I never got an answer to my mail on
this: http://www.mail-archive.com/dev%40maven.apache.org/msg42387.html
-Lukas
--
no easy way to figure generated source roots for a project
--
Key: MNG-1450
URL: http://jira.codehaus.org/browse/MNG-1450
Project: Maven 2
Type: Bug
Components: maven-embedder
Reporter: Milos Kleint
in
Thanks Jason.
Jason van Zyl a écrit :
Hi,
o code bases have been moved to apache
http://svn.apache.org/viewcvs.cgi/maven/doxia/
http://svn.apache.org/viewcvs.cgi/maven/surefire/
The tags appear to be in the wrong place for doxia and I didn't notice
that until the move but that's the way it wa
Hi,
o code bases have been moved to apache
http://svn.apache.org/viewcvs.cgi/maven/doxia/
http://svn.apache.org/viewcvs.cgi/maven/surefire/
The tags appear to be in the wrong place for doxia and I didn't notice
that until the move but that's the way it was on the codeahaus side.
o authorization
[ http://jira.codehaus.org/browse/CONTINUUM-426?page=comments#action_50215
]
Dan Allen commented on CONTINUUM-426:
-
My report seems a bit rushed because I was short on time. I do have detailed
error logs that I could provide, which I will upload as soo
Maven creates jar for a project without java sources
Key: MNG-1449
URL: http://jira.codehaus.org/browse/MNG-1449
Project: Maven 2
Type: Bug
Components: maven-jar-plugin
Versions: 2.0
Reporter: Giorg
[ http://jira.codehaus.org/browse/MNG-1387?page=comments#action_50209 ]
Erick Dovale commented on MNG-1387:
---
Does surefire support other test framework than junit?? Is there a plan to make
it support something else like testNG?
If not, then I think we wou
[ http://jira.codehaus.org/browse/MNG-1316?page=comments#action_50207 ]
Thomas Van de Velde commented on MNG-1316:
--
I have a nullpointer under these conditions:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-
[ http://jira.codehaus.org/browse/MEV-185?page=comments#action_50203 ]
Fabrice BELLINGARD commented on MEV-185:
And there is the same error for those dependencies:
log4j
log4j
1.2.6
logkit
logkit
[ http://jira.codehaus.org/browse/MEV-179?page=comments#action_50202 ]
Joerg Schaible commented on MEV-179:
The original POM is right. It references wsdl4j, which has not be uploaded to
ibiblio yet:
http://sourceforge.net/project/showfiles.php?group_id=
[
http://jira.codehaus.org/browse/MAVENUPLOAD-580?page=comments#action_50201 ]
Joerg Schaible commented on MAVENUPLOAD-580:
http://www.schaible.info/maven/wsdl4j-qname-1.5.1-bundle.jar
> Upload wsdl4j 1.5.1
> ---
>
> Key
Upload wsdl4j 1.5.1
---
Key: MAVENUPLOAD-580
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-580
Project: maven-upload-requests
Type: Task
Reporter: Joerg Schaible
WSDL 1.5.1 from
http://sourceforge.net/project/showfiles.php?group_id=128811&pa
On Mon, 2005-11-07 at 10:20 +1100, Brett Porter wrote:
> Hi,
>
> I was wondering what folks though of changing maven-artifact,
> maven-core, etc in JIRA to be user friendly components like:
>
> * error reporting
> * artifact deployment
> * artifact resolution
>
> etc.
+1
Anything the user can
commons-logging-1.0.4 POM dependencies not using properly
Key: MEV-185
URL: http://jira.codehaus.org/browse/MEV-185
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Fa
[ http://jira.codehaus.org/browse/MNG-1448?page=comments#action_50200 ]
Alexandre Poitras commented on MNG-1448:
Especially on the web site generated by maven. Something like an icon "Maven
2.0" would be nice.
> Easy way to tell if the plugin is fo
Easy way to tell if the plugin is for m2 or m1
--
Key: MNG-1448
URL: http://jira.codehaus.org/browse/MNG-1448
Project: Maven 2
Type: Bug
Components: maven-plugins
Reporter: Alexandre Poitras
--
This message is
[ http://jira.codehaus.org/browse/MEV-177?page=all ]
Tomislav Stojcevich reopened MEV-177:
-
It looks like all of them got updated except for the 1.0.2 version It's
timestamp changed like all the rest but the change is not in it. That's the
one
emma 2.0.latest : how do we handle this ?
-
Key: MEV-184
URL: http://jira.codehaus.org/browse/MEV-184
Project: Maven Evangelism
Type: Bug
Reporter: Yann Le Du
Versions of emma:emma are in the form 2.0.build
directory-net
Move common-test to its correct directory
-
Key: MEV-183
URL: http://jira.codehaus.org/browse/MEV-183
Project: Maven Evangelism
Type: Bug
Reporter: Yann Le Du
commons-test : commons-test : 0.1 is currently stored
[ http://jira.codehaus.org/browse/CONTINUUM-425?page=all ]
Emmanuel Venisse closed CONTINUUM-425:
--
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0.1
Done.
> Explain that uploading a POM file works only for a single pr
Replace ${pom.currentVersion} with ${pom.version} in apache-ldapber-provider
Key: MEV-182
URL: http://jira.codehaus.org/browse/MEV-182
Project: Maven Evangelism
Type: Bug
Reporter: Yann
Replace ${pom.currentVersion} with ${pom.version} in apacheds-main
--
Key: MEV-181
URL: http://jira.codehaus.org/browse/MEV-181
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Report
1 - 100 of 114 matches
Mail list logo
