Hi there,
I am new to Continuum and was wondering if it is possible to extend
Continuum by adding new project types. I'd like to add my own Add
XXX Project link on the Continuum page next to the other links for
Maven, Maven2, Ant, and Shell projects. Or alternatively if I could
use an API to add
You can't add an other type of project.
What is your project type?
We have a start of xmlrpc client in jira that can manage continuum, but it don't help you with new
project type.
Emmanuel
Knut Wannheden a écrit :
Hi there,
I am new to Continuum and was wondering if it is possible to
[ http://jira.codehaus.org/browse/CONTINUUM-385?page=comments#action_57523
]
Konstntin Polyzois commented on CONTINUUM-385:
--
Any news on this one?
run.sh on MacOS X fails with problem in wrapper
Knut Wannheden a écrit :
Emmanuel,
On 2/1/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
You can't add an other type of project.
What is your project type?
In our development enviroment we have our own project file format
(similar to Maven POM) and our own build tools on top of this.
Knut Wannheden a écrit :
I'd like to add projects with interdependencies to Continuum. Can I
also use the shell project type for this?
You can use the shell project type. You only need a command line to launch your
build.
Interdependencies between projects are available for now only for
Emmanuel,
I'm not sure I quite understand your question. But let me explain what
I'd like to do. We have 100+ projects in our development environment
and occasionally we add new projects and change the dependencies
between existing projects. We also change the developer list for the
[ http://jira.codehaus.org/browse/CONTINUUM-510?page=all ]
John Casey updated CONTINUUM-510:
-
Fix Version: (was: 1.1-alpha-1)
1.0.3
big year schedule 2099 prevents continuum from startup
[ http://jira.codehaus.org/browse/CONTINUUM-531?page=all ]
John Casey updated CONTINUUM-531:
-
Fix Version: (was: 1.1-alpha-1)
1.0.3
Add back the build now button on the view project page.
[ http://jira.codehaus.org/browse/CONTINUUM-567?page=all ]
John Casey updated CONTINUUM-567:
-
Fix Version: (was: 1.1-alpha-1)
1.0.3
A build must be launched if we have changes since last build (for same build
definition) and not
[ http://jira.codehaus.org/browse/CONTINUUM-354?page=all ]
John Casey updated CONTINUUM-354:
-
Fix Version: (was: 1.1-alpha-1)
1.0.3
Need a way to poll for new projects
---
Key:
[ http://jira.codehaus.org/browse/CONTINUUM-496?page=all ]
John Casey updated CONTINUUM-496:
-
Fix Version: (was: 1.1-alpha-1)
1.0.3
End Time contains junk value when I forced a build to run
all builds stuck in in progress/scheduled state
-
Key: CONTINUUM-576
URL: http://jira.codehaus.org/browse/CONTINUUM-576
Project: Continuum
Type: Bug
Components: Core system
Reporter: Brett Porter
Fix For:
Add Bazaar provider documentation
-
Key: SCM-147
URL: http://jira.codehaus.org/browse/SCM-147
Project: Maven SCM
Type: New Feature
Components: maven-scm-site
Reporter: Torbjørn EIkli Smørgrav
Priority: Minor
--
This
jerome lacoste wrote:
Sorry but it's not marked as such in Jira
http://jira.codehaus.org/browse/MASSEMBLY-19
Component/s: None
Affects Version/s:None
Fix Version/s:None
I know its a pain in the butt, but I will reiterate. We created the JIRA
projects *after* the
[ http://jira.codehaus.org/browse/MSITE-72?page=all ]
John Allen updated MSITE-72:
Attachment: SiteMojo.diff
new non reactor populateModules SiteMojo code assumes each POM declares its
own URL
Emmanuel,
On 2/1/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
You can't add an other type of project.
What is your project type?
In our development enviroment we have our own project file format
(similar to Maven POM) and our own build tools on top of this. The
reason we are not using any
On 2/1/06, Brett Porter [EMAIL PROTECTED] wrote:
jerome lacoste wrote:
Sorry but it's not marked as such in Jira
http://jira.codehaus.org/browse/MASSEMBLY-19
Component/s: None
Affects Version/s:None
Fix Version/s:None
I know its a pain in the butt, but I
Refactor of site:stage and site:site required due to new site:site modules
appraoch
---
Key: MSITE-84
URL: http://jira.codehaus.org/browse/MSITE-84
Project: Maven 2.x Site Plugin
Type:
Brett Porter wrote:
Thomas Recloux wrote:
I see two solutions:
- Keeping only one active proxy and add a way to specify multiple
protocols by proxy.
- Modify the Settings and DefaultMaven objects to add one active proxy
server by protocol.
What do you think of this? If you choose one of theses
JUnit addon: jfcunit
Key: MAVENUPLOAD-715
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-715
Project: maven-upload-requests
Type: Task
Reporter: Michael Böckling
Attachments: jfcunit-2.0.8-bundle.jar
jfcUnit enables developers to write
[ http://jira.codehaus.org/browse/MNG-1898?page=comments#action_57528 ]
Brian Fox commented on MNG-1898:
Any progress on this issue? I would like to move forward with my plugins but
can't because of this. We are stuck maintaining a bunch of lame ant scripts
Filtering should handle java.io.File values
---
Key: MRESOURCES-10
URL: http://jira.codehaus.org/browse/MRESOURCES-10
Project: Maven 2.x Resources Plugin
Type: Improvement
Reporter: Mike Perham
I'm trying to use filters
[ http://jira.codehaus.org/browse/MRESOURCES-10?page=all ]
Mike Perham updated MRESOURCES-10:
--
Description:
I'm trying to use filters along with ${basedir} to setup my unit test Derby
database. Derby must have a unique directory to build its database
[ http://jira.codehaus.org/browse/MRESOURCES-10?page=all ]
Mike Perham updated MRESOURCES-10:
--
Description:
I'm trying to use filters along with ${basedir} to setup my unit test Derby
database. Derby must have a unique directory to build its database
Stephane Nicoll wrote:
+1 for All except Jira-plugin +0 ; Dependency on Jira 3.3+ might be a
big issue. Had anyone sent a mail to the user list about it?
I don't think this is a big issue. The restriction to Jira 3.3+ was
necessary because of an API change in Jira itself, see
[ http://jira.codehaus.org/browse/MPPLUGIN-35?page=all ]
Lukas Theussl closed MPPLUGIN-35:
-
Resolution: Fixed
Now using ${maven.final.name}.jar everywhere. Plugins need standard names so
they can be uninstalled properly.
plugin:install fails if
jar:sign doesn't check if project prouces an artifact
-
Key: MJAR-27
URL: http://jira.codehaus.org/browse/MJAR-27
Project: Maven 2.x Jar Plugin
Type: Bug
Environment: Maven 2.0.2
Latest Jar checkout
Reporter:
[
http://jira.codehaus.org/browse/MAVENUPLOAD-715?page=comments#action_57550 ]
Carlos Sanchez commented on MAVENUPLOAD-715:
Version of the project is 2.08 not 2.0.8
JUnit addon: jfcunit
Key: MAVENUPLOAD-715
[
http://jira.codehaus.org/browse/MAVENUPLOAD-686?page=comments#action_57551 ]
Carlos Sanchez commented on MAVENUPLOAD-686:
As stated in the documentation for uploads, I won't upload this to
jxta - wrong groupIds, now we use fully qualified
[ http://jira.codehaus.org/browse/MAVENUPLOAD-708?page=all ]
Carlos Sanchez closed MAVENUPLOAD-708:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Hibernate Annotations 3.1 beta 8 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-712?page=all ]
Carlos Sanchez closed MAVENUPLOAD-712:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Upload hibernate-tools-3.1.0.beta4
--
Key:
[ http://jira.codehaus.org/browse/MAVENUPLOAD-715?page=all ]
Michael Böckling updated MAVENUPLOAD-715:
-
Attachment: jfcunit-2.08-bundle.jar
JUnit addon: jfcunit
Key: MAVENUPLOAD-715
URL:
[ http://jira.codehaus.org/browse/MPJAVA-8?page=all ]
Lukas Theussl closed MPJAVA-8:
--
Resolution: Fixed
Closing now that MPPLUGIN-35 is fixed, I don't see any other place where this
is still an issue. The war case won't be fixed for backwards
[ http://jira.codehaus.org/browse/MPPLUGIN-30?page=all ]
Lukas Theussl updated MPPLUGIN-30:
--
Fix Version: 1.7.1
Can't we simply add a property to choose whether plugins get installed in
maven.plugin.dir or maven.plugin.user.dir?
Plugins on a
[ http://jira.codehaus.org/browse/ARCHETYPE-23?page=comments#action_57555 ]
John Didion commented on ARCHETYPE-23:
--
I've modified archetype-core and archetype-plugin to provide this functionality
for our projects. I'll attache the code I modified to
[ http://jira.codehaus.org/browse/ARCHETYPE-23?page=all ]
John Didion updated ARCHETYPE-23:
-
Attachment: MavenArchetypeMojo.java
archetype.mdo
DefaultArchetype.java
Possibility to create real multiple modules with Java
[ http://jira.codehaus.org/browse/MAVENUPLOAD-707?page=all ]
Geoffrey De Smet updated MAVENUPLOAD-707:
-
Attachment: pom.xml
Glazedlists 1.5.0
-
Key: MAVENUPLOAD-707
URL:
jerome lacoste wrote:
Note I am not trying to be a pain in the butt here.
:) I meant I know the fact that the issue could have been moved up to
2.0.1 was the pain, not you.
I am just saying
that there was something that could have been done better and that I
hope won't happen again.
I'm
On 2/1/06, Lukas Theussl [EMAIL PROTECTED] wrote:
Stephane Nicoll wrote:
+1 for All except Jira-plugin +0 ; Dependency on Jira 3.3+ might be a
big issue. Had anyone sent a mail to the user list about it?
That's why I said
on the web page 'needs at least JIRA 3.3 to work properly' and
I found this:
http://confluence.atlassian.com/pages/viewpage.action?pageId=121422
Vincent, could you help us set this up in our workflow?
Thanks,
Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
IMO, Just document it, and maybe which plugin version works with 3.3.
- Brett
Lukas Theussl wrote:
Stephane Nicoll wrote:
+1 for All except Jira-plugin +0 ; Dependency on Jira 3.3+ might be a
big issue. Had anyone sent a mail to the user list about it?
I don't think this is a big
Easy access to dependency jars
--
Key: MANTRUN-41
URL: http://jira.codehaus.org/browse/MANTRUN-41
Project: Maven 2.x Antrun Plugin
Type: New Feature
Versions: 1.1
Reporter: Patrick Lightbody
Fix For: 1.2
It would be
[ http://jira.codehaus.org/browse/MANTRUN-41?page=all ]
Kenney Westerhof closed MANTRUN-41:
---
Resolution: Fixed
Fixed in revision 374150. I chose to define properties:
maven.dependency.groupId.artifactId.type.path,
so for instance:
[ http://jira.codehaus.org/browse/MANTRUN-35?page=all ]
Kenney Westerhof closed MANTRUN-35:
---
Assign To: Kenney Westerhof (was: Jason van Zyl)
Resolution: Fixed
Fixed in revision 374152: when -X is specified, the loglevel
is set to 'debug'.
[ http://jira.codehaus.org/browse/CONTINUUM-519?page=all ]
John Casey reopened CONTINUUM-519:
--
scheduler not calling scm's update command at scheduled time
Key: CONTINUUM-519
[ http://jira.codehaus.org/browse/CONTINUUM-519?page=all ]
John Casey updated CONTINUUM-519:
-
Fix Version: (was: 1.1-alpha-1)
1.0.3
scheduler not calling scm's update command at scheduled time
[ http://jira.codehaus.org/browse/CONTINUUM-519?page=all ]
John Casey closed CONTINUUM-519:
Resolution: Fixed
scheduler not calling scm's update command at scheduled time
[ http://jira.codehaus.org/browse/CONTINUUM-507?page=all ]
John Casey reopened CONTINUUM-507:
--
detect and repair svn problems by running svn cleanup
-
Key: CONTINUUM-507
URL:
[ http://jira.codehaus.org/browse/CONTINUUM-535?page=all ]
John Casey reopened CONTINUUM-535:
--
Trigger a build if change set doesn't contains only files with unknown status
[ http://jira.codehaus.org/browse/CONTINUUM-507?page=all ]
John Casey closed CONTINUUM-507:
Resolution: Fixed
Fix Version: (was: 1.1-alpha-1)
1.0.3
detect and repair svn problems by running svn cleanup
[ http://jira.codehaus.org/browse/CONTINUUM-535?page=all ]
John Casey closed CONTINUUM-535:
Resolution: Fixed
Fix Version: (was: 1.1-alpha-1)
1.0.3
Trigger a build if change set doesn't contains only files with unknown
[ http://jira.codehaus.org/browse/CONTINUUM-514?page=all ]
John Casey reopened CONTINUUM-514:
--
Consistency in layout of Continuum download page to the Maven 2.0 download
page
[ http://jira.codehaus.org/browse/CONTINUUM-514?page=all ]
John Casey closed CONTINUUM-514:
Resolution: Fixed
Fix Version: (was: 1.1-alpha-1)
1.0.3
Consistency in layout of Continuum download page to the Maven 2.0
[ http://jira.codehaus.org/browse/CONTINUUM-527?page=all ]
John Casey updated CONTINUUM-527:
-
Fix Version: 1.0.3
Getting Started Documentation omits JAVA_HOME requirement
-
Key:
[ http://jira.codehaus.org/browse/CONTINUUM-532?page=all ]
John Casey reopened CONTINUUM-532:
--
Add ability to move from a particular build to the build list for a project.
[ http://jira.codehaus.org/browse/CONTINUUM-532?page=all ]
John Casey closed CONTINUUM-532:
Resolution: Fixed
Fix Version: (was: 1.1-alpha-1)
1.0.3
Add ability to move from a particular build to the build list for a
[ http://jira.codehaus.org/browse/CONTINUUM-543?page=all ]
John Casey updated CONTINUUM-543:
-
Fix Version: 1.0.3
please add reference to netbeans continuum integration from the the continuum
site
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060201.21.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060201.21.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MANTRUN-32?page=all ]
Kenney Westerhof closed MANTRUN-32:
---
Assign To: Kenney Westerhof
Resolution: Fixed
Fixed in revision 374157. Added missing call to Project.init().
ant tasks don't use correct
[ http://jira.codehaus.org/browse/CONTINUUM-555?page=all ]
John Casey updated CONTINUUM-555:
-
Fix Version: (was: 1.1)
1.0.3
Continuum only executes default build-definition
[ http://jira.codehaus.org/browse/CONTINUUM-449?page=all ]
John Casey closed CONTINUUM-449:
Resolution: Fixed
Fix Version: (was: 1.1)
1.0.3
title bar says Jabber when creating an MSN notifier
[ http://jira.codehaus.org/browse/CONTINUUM-449?page=all ]
John Casey reopened CONTINUUM-449:
--
title bar says Jabber when creating an MSN notifier
-
Key: CONTINUUM-449
URL:
[ http://jira.codehaus.org/browse/MCHECKSTYLE-27?page=comments#action_57564
]
Vincent Massol commented on MCHECKSTYLE-27:
---
I just wanted to say that I have tried it again with checkstyle plugin v2.0 and
it's not working any better
[ http://jira.codehaus.org/browse/CONTINUUM-544?page=all ]
John Casey updated CONTINUUM-544:
-
Fix Version: (was: 1.1)
1.0.3
there is no xmlrpc client code for contacting the server.
some thoughts:
- This omits classifier, in the case it differs from type
- isn't this verbose if you have to give jar all the time, when most
dependencies are?
- does this handle dotted group IDs? (I assume it does)
I thought it might be better to do a taskdef (which I assume the antrun
plugin
[ http://jira.codehaus.org/browse/CONTINUUM-537?page=all ]
John Casey updated CONTINUUM-537:
-
Fix Version: (was: 1.1)
1.0.3
Guests cannot see totals
Key: CONTINUUM-537
URL:
[ http://jira.codehaus.org/browse/CONTINUUM-518?page=all ]
John Casey updated CONTINUUM-518:
-
Fix Version: 1.0.3
Top directory files in project (ie: pom.xml) not updated from CVS on
subsequent builds.
[ http://jira.codehaus.org/browse/MANTRUN-40?page=comments#action_57565 ]
Kenney Westerhof commented on MANTRUN-40:
-
It's impossible to propagate all properties to the called ant buildfile, since
only listed properties
are propagated. Most
[ http://jira.codehaus.org/browse/MCHECKSTYLE-27?page=all ]
Vincent Massol updated MCHECKSTYLE-27:
--
Description:
Here's the config I have:
{code:xml}
build
plugins
plugin
artifactIdmaven-checkstyle-plugin/artifactId
[ http://jira.codehaus.org/browse/MANTRUN-40?page=comments#action_57566 ]
Brett Porter commented on MANTRUN-40:
-
what about if the plugin depended on the maven-artifact-ant antlib (the thin
jar + transitive deps, not the fat one), and registered that
[ http://jira.codehaus.org/browse/MCHECKSTYLE-27?page=all ]
Vincent Massol updated MCHECKSTYLE-27:
--
Description:
Here's the config I have:
{code:xml}
build
plugins
plugin
artifactIdmaven-checkstyle-plugin/artifactId
[ http://jira.codehaus.org/browse/MANTRUN-37?page=comments#action_57567 ]
Kenney Westerhof commented on MANTRUN-37:
-
I see two different problems here. Mike; if you purge
~/.m2/repository/org/apache/maven/plugins/ do you still have
problems? It
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060201.201500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060201.201500.txt
-
To unsubscribe,
On Thu, 2 Feb 2006, Brett Porter wrote:
some thoughts:
- This omits classifier, in the case it differs from type
Right, will fix.
- isn't this verbose if you have to give jar all the time, when most
dependencies are?
I don't think those 4 characters are going to bother the users as much
as
XML test reports are not well-formed when failure message contains quotes.
--
Key: MSUREFIRE-54
URL: http://jira.codehaus.org/browse/MSUREFIRE-54
Project: Maven 2.x Surefire Plugin
Type: Bug
[ http://jira.codehaus.org/browse/MANTRUN-41?page=all ]
Carlos Sanchez reopened MANTRUN-41:
---
Some comments:
- you're breaking api compatability with previous version changing constructor
arguments
- you've added a new feature with no documentation
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060201.203001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060201.203001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MANTRUN-32?page=all ]
Carlos Sanchez reopened MANTRUN-32:
---
Again breaking api, you should deprecate methods instead of removing.
ant tasks don't use correct environment in antrun plugin
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: mercredi 1 février 2006 20:57
To: Maven Developers List
Subject: editing closed JIRA issues
I found this:
http://confluence.atlassian.com/pages/viewpage.action?pageId=121422
Vincent, could you help us set
[ http://jira.codehaus.org/browse/MANTRUN-40?page=comments#action_57570 ]
Jason Dillon commented on MANTRUN-40:
-
Sorry Kenny, but properties *do not* actually make it into the ant's execution
environment. Properties are only resolved in the pom (tasks
[ http://jira.codehaus.org/browse/MANTRUN-41?page=comments#action_57571 ]
Kenney Westerhof commented on MANTRUN-41:
-
- about the AntPropertyHelper: it's supposed to be a package private class, not
part of any public API.
But I'll add the original
[ http://jira.codehaus.org/browse/MANTRUN-32?page=all ]
Kenney Westerhof closed MANTRUN-32:
---
Resolution: Fixed
sorry! committed @ rev 374173
ant tasks don't use correct environment in antrun plugin
[ http://jira.codehaus.org/browse/MSITE-84?page=all ]
Brett Porter updated MSITE-84:
--
Fix Version: 2.0
hmm, ok. I hadn't thought this was what site:stage was doing.
Refactor of site:stage and site:site required due to new site:site modules
appraoch
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060201.21.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060201.21.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
um, not quite :)
1) the equals check is redundant
2) type + classifier is valid
I think its just a simple append of .${classifier} if it is not null.
[EMAIL PROTECTED] wrote:
Author: kenney
Date: Wed Feb 1 12:56:07 2006
New Revision: 374170
URL:
[
http://jira.codehaus.org/browse/MAVENUPLOAD-686?page=comments#action_57575 ]
Loic Lefevre commented on MAVENUPLOAD-686:
--
Okay, after some brainstorming on the dev mailing list, the following groupId
has been chosen for this artifact:
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060201.211500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060201.211500.txt
-
To unsubscribe,
It's not possible to replace the existing Maven workflow?
Vincent Massol wrote:
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: mercredi 1 février 2006 20:57
To: Maven Developers List
Subject: editing closed JIRA issues
I found this:
Brett Porter wrote:
It's not possible to replace the existing Maven workflow?
I can certainly flip them but it would be easier to just edit the
existing workflow.
Vincent Massol wrote:
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: mercredi 1 février 2006
Hibernate 3.1.x POMs pull in Sun jars
-
Key: MEV-320
URL: http://jira.codehaus.org/browse/MEV-320
Project: Maven Evangelism
Type: Bug
Components: Dependencies
Reporter: Mike Perham
jta and jacc need to be scoped as
[ http://jira.codehaus.org/browse/MEV-320?page=comments#action_57584 ]
Carlos Sanchez commented on MEV-320:
I don't know about using hibernate in a full app server but what happens if you
want to use jta transactions in a web container like tomcat?
To Whom it may concern:
M2_ HOME is set to E:\JUtils\maven-2.0.1-frmSrc and I'm getting the
following error
//--
ERROR: M2_HOME is set to an invalid
Why don't you try with the last version 2.0.2
On 2/1/06, Waldo Ford [EMAIL PROTECTED] wrote:
To Whom it may concern:
M2_ HOME is set to E:\JUtils\maven-2.0.1-frmSrc and I'm getting the
following error
//--
[ http://jira.codehaus.org/browse/MEV-320?page=comments#action_57585 ]
Mike Perham commented on MEV-320:
-
I would think you would need to pull in an XA engine like JOTM too so this
wouldn't be a showstopper. Perhaps it should be marked as optional?
Make -X show maven version as first thing
-
Key: MNG-2030
URL: http://jira.codehaus.org/browse/MNG-2030
Project: Maven 2
Type: Improvement
Components: Command Line
Versions: 2.0.2
Reporter: Carlos Sanchez
[ http://jira.codehaus.org/browse/MNG-2030?page=all ]
Carlos Sanchez updated MNG-2030:
Fix Version: 2.0.3
Make -X show maven version as first thing
-
Key: MNG-2030
URL:
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060202.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060202.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[ http://jira.codehaus.org/browse/MPSCM-76?page=all ]
Lukas Theussl closed MPSCM-76:
--
Resolution: Fixed
Make scm plugin independent of release
--
Key: MPSCM-76
URL:
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060202.003002.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Validate the configuration
---
Key: MSUREFIRE-55
URL: http://jira.codehaus.org/browse/MSUREFIRE-55
Project: Maven 2.x Surefire Plugin
Type: Improvement
Versions: 2.1.2
Reporter: Jason van Zyl
Fix For: 2.1.3
Currently
1 - 100 of 127 matches
Mail list logo