Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060125.073000.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060125.073000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
> move this to maven dev for more visibility.
>
Thanks.
> sasvata, have you seen my reply in the JIRA?
Nope, not until you mentioned it. I thought I'd get comments if I
were the originator (used to DDTS :-), but I guess I have to watch the
issue.
-
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060125.071501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060125.071501.txt
-
To unsubscribe, e-mai
Forgot to mention: I will implement your suggestion before submitting a patch.
> > sasvata, have you seen my reply in the JIRA?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MNG-1301?page=all ]
Allan Ramirez closed MNG-1301:
--
Resolution: Fixed
added in the SVN, in howto.apt of surefire plugin.
> Document test inclusions and exclusions using the surefire plugin
>
[ http://jira.codehaus.org/browse/MRM-55?page=all ]
Edwin Punzalan closed MRM-55:
-
Resolution: Fixed
Patch applied. Thanks.
> don't add duplicates to the index
> -
>
> Key: MRM-55
> URL: http://jira.cod
> Hi Brett,
> I installed /repos/asf/maven/skins/trunk on my machine but I still ended
> up getting this.
> This is what i did
> 1. checkout http://svn.apache.org/repos/asf/maven/plugins/trunk/ plugins
> 2. mvn install on plugins
> 3. checkout http://svn.apache.org/repos/asf/maven/skins/trunk skin
[ http://jira.codehaus.org/browse/MRM-55?page=all ]
Maria Odea Ching updated MRM-55:
Attachment: MRM-55-maven-repository-indexer.patch
> don't add duplicates to the index
> -
>
> Key: MRM-55
> URL: http:/
Hi Brett,
I installed /repos/asf/maven/skins/trunk on my machine but I still ended up
getting this.
This is what i did
1. checkout http://svn.apache.org/repos/asf/maven/plugins/trunk/ plugins
2. mvn install on plugins
3. checkout http://svn.apache.org/repos/asf/maven/skins/trunk skins
4 mvn instal
[ http://jira.codehaus.org/browse/MNGECLIPSE-57?page=comments#action_56871
]
Leonardo Quijano Vincenzi commented on MNGECLIPSE-57:
-
The plugin works, it just takes too long to compile (longer than normal MVN).
I'll check the logs ASAP to
[ http://jira.codehaus.org/browse/MRM-55?page=all ]
Maria Odea Ching updated MRM-55:
Attachment: MRM-55-maven-repository-indexer.patch
> don't add duplicates to the index
> -
>
> Key: MRM-55
> URL: http:/
[ http://jira.codehaus.org/browse/MNG-1938?page=comments#action_56868 ]
Ørjan Austvold commented on MNG-1938:
-
It is totally reproducible on a project we have have at work.
The failure is occuring each time when I upload the site to a CentOS machine.
I
[ http://jira.codehaus.org/browse/MNGECLIPSE-57?page=all ]
Eugene Kuleshov updated MNGECLIPSE-57:
--
Summary: Unable to download the artifact from any repository (was: M2
plugin looks for "" repository folder)
Message "Local repository folder "" doe
[ http://jira.codehaus.org/browse/MNGECLIPSE-57?page=comments#action_56865
]
Leonardo Quijano Vincenzi commented on MNGECLIPSE-57:
-
Not at all. Direct internet connection, and I haven't touched settings.xml
This problem appeared when refr
move this to maven dev for more visibility.
sasvata, have you seen my reply in the JIRA?
On 1/24/06, Sasvata Chatterjee <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> This is regarding the JIRA issue I submitted:
> http://jira.codehaus.org/browse/PLX-186.
>
> Basically, the Maven2 dependency-maven-plugi
Brett, so you are okie with duplicate definitions in both .mod file for
http://jira.codehaus.org/browse/MASSEMBLY-62
?
-Dan
On 1/24/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> not right now. There is an open JIRA to implement some form of
> inheritence.
>
> - Brett
>
> dan tran wrote:
>
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060125.021501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060125.021501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56862
]
Eugene Kuleshov commented on MNGECLIPSE-56:
---
Can you tell windows firewall to do not allow connection to debug port?
It is also unclear if attached log is related to the
[ http://jira.codehaus.org/browse/MRM-38?page=comments#action_56861 ]
John Tolentino commented on MRM-38:
---
Will reuse plexus-quartz component. Will add to webapp component and trigger a
schedule.
> add a background task scheduler
> ---
Anyone want to update:
clean, ear, ejb, jar, plugin, rar, war, compiler, resources, source,
ant, antlr, release, repository, idea, eclipse, verifier, checkstyle,
clover, javadoc, projectinforeports below?
I'll pass back over this and fill in the gaps at the end of the month,
then this will become
I've been working on the site plugin.
I'll resend my mail where I was asking for updates from people, which
was my attempt to do this.
I don't think allotting owners works or is in sync with community spirit
(obligating someone in particular when they may or may not have time).
It just takes some
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56860
]
Dmitri Maximovich commented on MNGECLIPSE-56:
-
Yes, I have tried to run Eclipse and/or builder unde jre 1.5.0_06 - don't see
any troubles.
Indeed it can be issue with f
Agreed, but it's hard to have a roadmap when you don't have definitive
owners with known schedules. I would like to see the same for the site
plugin.
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 24, 2006 6:06 PM
To: Maven Developers List
Subject:
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20060125.013001.war
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20060125.013001.txt
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060125.013001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060125.013001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
NPE when -Dplugin value can not find specified plugin
-
Key: MPH-10
URL: http://jira.codehaus.org/browse/MPH-10
Project: Maven 2.x Help Plugin
Type: Bug
Versions: 2.0
Reporter: Barrie Treloar
specifyi
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060125.011501.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The Maven Help plugin provides goals aimed at helping to make sense out of
the build environment. It includes the ability to view the effective
POM and settings files, after inheritance and active profiles
have been applied, as well as a describe a particular plugin goal to
give usage information.
not right now. There is an open JIRA to implement some form of inheritence.
- Brett
dan tran wrote:
> Hello,
>
> I have 2 .mdo files which share some classes. Currently I have both files
> containing same share class definitions.
>
> Is there a better way?
>
> Thanks
>
> -Dan
>
--
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56858
]
Eugene Kuleshov commented on MNGECLIPSE-56:
---
By the way, Kess, is there are any local firewall running on you windows
machine?
I've had some issues with Java debugger wh
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060125.010002.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060125.010002.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56857
]
Eugene Kuleshov commented on MNGECLIPSE-56:
---
Dmitri, have you tried to run Eclipse using JRE? You can also try to point m2
launcher to JRE...
> Exception running M2 buil
Hello,
I have 2 .mdo files which share some classes. Currently I have both files
containing same share class definitions.
Is there a better way?
Thanks
-Dan
[ http://jira.codehaus.org/browse/MNGECLIPSE-56?page=comments#action_56856
]
Dmitri Maximovich commented on MNGECLIPSE-56:
-
I cannot reproduce the issue:
-Fresh installation of Eclipse 3.1.1 on Windows, no extra plugins. JDK 1.5.0_05
and _06.
fix URL of JIRA plugin projects
---
Key: MPA-44
URL: http://jira.codehaus.org/browse/MPA-44
Project: Maven Project Administration
Type: Bug
Components: Issue Management
Reporter: Brett Porter
Assigned to: Jason van Zyl
Prior
[ http://jira.codehaus.org/browse/CONTINUUM-569?page=comments#action_56855
]
Richard C. L. Li commented on CONTINUUM-569:
Besides fixing the validator, I think codes in application startup should be
fixed as well so that the application can stae
rename m1 plugins in JIRA
-
Key: MPA-43
URL: http://jira.codehaus.org/browse/MPA-43
Project: Maven Project Administration
Type: Improvement
Components: Issue Management
Reporter: Brett Porter
Assigned to: Jason van Zyl
Fix For:
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060125.003000.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1 Binding: John, Brett, Arnaud, Lukas, Emmanuel, Vincent S
+1 Non-binding: Mike, Alex, Dan
I'll proceed with the release
-- Forwarded message --
From: Carlos Sanchez <[EMAIL PROTECTED]>
Date: Jan 20, 2006 11:52 AM
Subject: [Vote] Release assembly plugin 2.0.1
To: Maven Developers
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060125.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060125.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MNG-868?page=comments#action_56854 ]
John Didion commented on MNG-868:
-
This is also an issue for plugins that use properties. The plugin documentation
states:
Properties
This category covers any map which implements java.
[ http://jira.codehaus.org/browse/MNGECLIPSE-57?page=comments#action_56853
]
Eugene Kuleshov commented on MNGECLIPSE-57:
---
Are you behind proxy, firewall or defined some private repositories in
settings.xml?
> M2 plugin looks for "" repository fol
There was some discussion on this list a while back about setting
certain plugins to get releases scheduled along with maven releases. Was
this ever resolved? The plugins make up such a large portion of this
project that it is important they get some scheduled lifecycle. It's
great to see focus on
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060124.234500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060124.234500.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MNG-1677?page=all ]
Dennis Lundberg updated MNG-1677:
-
Attachment: MVN-1677.patch
> SCM docs in project reference
> -
>
> Key: MNG-1677
> URL: http://jira.codehaus.org/browse
Was this necessary, or just done for consistency?
Need to ask Arnaud about that.
You *have* to use the nsis plugin to do a Windows release of Maven.
Acknowledged, nsis will stay.
I agree with demoting jcoverage, thinking more about it.
:)
-Lukas
+1 to src/it
-1 to 2.0.3, I'd rather have a stable 2.0.x without new features and
have a early 2.1 with the new stuff postponing new features not
implemented to 2.2
On 1/23/06, Vincent Massol <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In order to progress on the topic of integration testing, I'm proposi
Lukas Theussl wrote:
> At least cruisecontrol and jcoverage have had some dependencies updated
> to match them with the maven core. So if we want to include them in
> m1.1, we have to re-release them.
Was this necessary, or just done for consistency?
> But as I said, my main concern is that I am
+1 for src/it
I've got to say I'm greatly hesitant to add new things to 2.0.3, but it
wouldn't be the first time. Be careful :)
How sure are we that this will be the final solution - are new test
types needed?
Just trying to get a grip on where we are at with the topic as a whole.
- Brett
Vinc
With the exception of nsis (which is required to release Maven!), the
current state is likely identical to the last release, so leaving them
as is seems fine.
At least cruisecontrol and jcoverage have had some dependencies updated
to match them with the maven core. So if we want to include th
This looks good to me at first blush. Please make sure this gets
captured in the wiki.
As far as the matric registry goes, if you use a singleton component
then you will guarantee each gets the same. Is that what you needed?
/** @component */
private MetricRegistry registry;
This is going to nee
Fabrizio Giustina wrote:
> mh, you are right: this works but the "build-tools" dependency will
> end up as an (unwanted) project dependency... anyway, a plugin-level
> dependency doesn't work and it's not valid according to the xsd.
>
> I see this note in Brett commit:
> "don't recommend using ext
[ http://jira.codehaus.org/browse/MNG-1895?page=all ]
Carlos Sanchez updated MNG-1895:
Summary: Dependencies in two paths are not added to resolution when scope
needs to be updated in the nearest due to any of nearest parents (was:
Dependencies in two
[ http://jira.codehaus.org/browse/MNG-1895?page=all ]
Carlos Sanchez closed MNG-1895:
---
Resolution: Fixed
> Dependencies in two paths are not added to resolution when scope needs to be
> updated in the nearest due to any of nearest parents
>
And the other project is a dependency of the current project, and you
use OtherProjectsClass.class.getResource() ?
I'm pretty sure this works. Perhaps you could provide us with an
integration test that demonstrates the problem?
- Brett
Thomas Van de Velde wrote:
> A unit test in a project tries
I'd need to look into the code. I know surefire creates an isolated
classloader but I don't know how that is being applied to the test NG
support.
I assume this is with Jesse Kuhnert's recent work? I'll try and review
that on the plane on the way home...
- Brett
Michael Fiedler wrote:
> My quest
For this specific case, I'm not sure I understand. "Build time"
dependencies are always specified as one of the following:
* dependency of a plugin (added in the plugin's POM)
* customised dependency of a plugin (added inside the plugin element of
the project POM)
* an extension to the build system
document clean and site lifecycles
--
Key: MNG-2008
URL: http://jira.codehaus.org/browse/MNG-2008
Project: Maven 2
Type: Bug
Components: documentation - introductions
Versions: documentation
Reporter: Brett Porter
[ http://jira.codehaus.org/browse/MDEPLOY-22?page=all ]
Brett Porter closed MDEPLOY-22:
---
Assign To: Brett Porter
Resolution: Won't Fix
Fix Version: (was: 2.2)
will do
> distributionManagement/repository shouldn't be required
>
No, multiple active proxies doesn't make any sense. The only reason for
multiple active ones is possibly to support a different active one per
protocol, but I imagine even that would be very infrequent.
- Brett
Scokart Gilles wrote:
> I'm looking at a the support of the proxies in the site:deplo
I'd guess use the full URL.
- Brett
Dennis Lundberg wrote:
> Dennis Lundberg wrote:
>> I'm creating a patch for MNG-1677 and need to know what the policy is
>> for linking between sites for different parts of Maven.
>>
>> In this case I need to create a link from maven-components
>> (maven-model)
[ http://jira.codehaus.org/browse/MDEPLOY-22?page=comments#action_56849 ]
Matthew Beermann commented on MDEPLOY-22:
-
Is that a phase or a goal? Either way, it's undocumented AFAICT... if it does
what I'm trying for here, then morph this bug into a do
Does this not still work? All it does it create bundles that people can
submit to JIRA.
Yes it works. As mentioned above, I will move it into artifact. OK?
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
[ http://jira.codehaus.org/browse/MNG-1455?page=all ]
Brett Porter closed MNG-1455:
-
Resolution: Duplicate
> Possible NPE in DefaultArtifactResolver
> ---
>
> Key: MNG-1455
> URL: http://jira.codehau
[ http://jira.codehaus.org/browse/MDEPLOY-22?page=comments#action_56847 ]
Brett Porter commented on MDEPLOY-22:
-
what;s wrong with site-deploy?
> distributionManagement/repository shouldn't be required
> --
M2 plugin looks for "" repository folder
Key: MNGECLIPSE-57
URL: http://jira.codehaus.org/browse/MNGECLIPSE-57
Project: Maven 2.x Extension for Eclipse
Type: Bug
Versions: 0.0.4
Environment: Windows XPSP1, MyEclipse
[ http://jira.codehaus.org/browse/MDEPLOY-22?page=comments#action_56846 ]
Matthew Beermann commented on MDEPLOY-22:
-
I've got site:site and site:deploy attached to the deploy phase, which seems
like a reasonable sort of thing to do. As such, my
sec
IIRC, touchstone tests it.
Lukas Theussl wrote:
>
> Thanks Brett, but there is still
> http://jira.codehaus.org/browse/MAVEN-1630 to be clarified which is
> obviously not a proper use of the element . However, I
> can't find any use cases for this element, is that somewhere documented?
> Any exa
[ http://jira.codehaus.org/browse/MNG-1455?page=comments#action_56845 ]
Bernd Bohmann commented on MNG-1455:
I think it it fixed in the latest version.
But I see from time to time a message on the list NPE in
DefaultArtifactResolver ..
Or is this not th
Thanks Brett, but there is still
http://jira.codehaus.org/browse/MAVEN-1630 to be clarified which is
obviously not a proper use of the element . However, I
can't find any use cases for this element, is that somewhere documented?
Any examples how a plugin might use it?
-Lukas
Brett Porter
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060124.224500.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Lukas Theussl wrote:
Hello again,
Plugins to demote with work to do:
[] repository - (do we need upload-bundle? I don't see where it's used)
Does this not still work? All it does it create bundles that people can
submit to JIRA.
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apa
Lukas Theussl wrote:
> Discussed that with Carlos, I will move the create-upload-bundle goal
> into the artifact plugin. OK?
I guess so.
> So you'd say we include the latest stable version or just re-release in
> the current state?
With the exception of nsis (which is required to release Maven!
[ http://jira.codehaus.org/browse/MAVEN-1693?page=all ]
Brett Porter closed MAVEN-1693:
---
Assign To: Brett Porter
Resolution: Won't Fix
just because we aren't using it doesn't mean other plugins aren't.
> Remove unused from POM model, documentat
[ http://jira.codehaus.org/browse/MNG-2004?page=all ]
Brett Porter closed MNG-2004:
-
Assign To: Brett Porter
Resolution: Won't Fix
to be handled repository side, see MRM project
> repository:bundle-create should check that dependent artifacts are
[ http://jira.codehaus.org/browse/MNG-1455?page=comments#action_56838 ]
Brett Porter commented on MNG-1455:
---
the patch should *not* be applied. The file should not be null once the
artifact is resolved.
Does the problem still exist with the latest project
[ http://jira.codehaus.org/browse/MNG-1938?page=comments#action_56836 ]
Brett Porter commented on MNG-1938:
---
Does anyone have a reproducible case with Maven 2.0.2? As I said, it's fine for
me.
> site:deploy hangs forever on remote upack command
>
[] repository - (do we need upload-bundle? I don't see where it's used)
don't we need to keep the bundle stuff?
Discussed that with Carlos, I will move the create-upload-bundle goal
into the artifact plugin. OK?
[] antlr
[] cruisecontrol
[] jcoverage - replaced by Cobertura
[] jdif
[ http://jira.codehaus.org/browse/MDEPLOY-22?page=comments#action_56835 ]
Brett Porter commented on MDEPLOY-22:
-
what goal are you running? I don't understand what you expect deploy to do
without it.
> distributionManagement/repository shouldn't be requ
OK. Just assign the issue to me, I'll do it.
Thanks! I will open issues as soon as the vote is finalized.
Personally, +1. I am surprised to see the JBoss plugin there though.
Any contact with the JBoss people? (Maybe someone there can maintain
it)
No idea. Maybe Vincent M has some contact
Lukas Theussl wrote:
Last time I checked the the scm plugin used code from the release
plugin - the "release:transform" taglib.
That's why I said 'move used classes to SCM plugin'.
Sorry, missed that part :(
In M2 the pom transformation is handled by the release-plugin.
An alternative
Lukas Theussl wrote:
> Plugins to demote with work to do:
>
> [] repository - (do we need upload-bundle? I don't see where it's used)
don't we need to keep the bundle stuff?
> [] release - move used classes to SCM plugin (Fabrizio?)
+1
> [] j2ee - move the resolver tag into ear and j2ee:valida
On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> Hello again,
>
> [] j2ee - move the resolver tag into ear and j2ee:validate-war to
> war:validate (Stephane?)
OK. Just assign the issue to me, I'll do it.
> Other unmaintained plugins:
>
> [] abbot
> [] antlr
> [] castor - not working (see MP
On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I'd like to call for a vote on the following m1 plugin releases:
[+1] maven-changelog-plugin-1.9
[+1] maven-file-activity-plugin-1.6
[+1] maven-developer-activity-plugin-1.6
[+1] maven-simian-plugin-1.6
fabrizio
-
Does that mean we should remove it from the documentation (see
http://jira.codehaus.org/browse/MAVEN-1693)?
-Lukas
Brett Porter wrote:
I believe it existed before, but was unused.
- Brett
Arnaud HERITIER wrote:
Hi Lukas,
I saw your message on the IRC.
I think that properties under t
+1
Lukas Theussl wrote:
>
> Hi,
>
> I'd like to call for a vote on the following m1 plugin releases:
>
> [] maven-changelog-plugin-1.9
> [] maven-file-activity-plugin-1.6
> [] maven-developer-activity-plugin-1.6
> [] maven-simian-plugin-1.6
>
> The changelog plugin is the only one with major b
I believe it existed before, but was unused.
- Brett
Arnaud HERITIER wrote:
> Hi Lukas,
>
> I saw your message on the IRC.
> I think that properties under the project node were never used in m1.
> It was certainly added to prepare the compatibility with m2.
> None of our plugins use them
No idea, can't get to the page to check right now either.
Emmanuel Venisse wrote:
> Brett,
>
> Do you know what's happen with
> plexus:plexus-container-default:jar:1.0-alpha-5 dependency?
>
> I'll try to update later maven-scm-manager-plexus with a more recent
> plexus container.
>
> Emmanuel
>
I'd suggest a manual move. Looking at what was added to the wiki
recently (eg, the installation instructions), I couldn't really tell the
difference between that and the docs on the website...
- Brett
Stephen Duncan wrote:
> As I'm sure you've seen from messages on the list, this wiki has been
>
[ http://jira.codehaus.org/browse/MNG-1895?page=all ]
Carlos Sanchez updated MNG-1895:
Summary: Dependencies in two paths are not added to resolution when scope
needs to be updated in the nearest (was: Scopes are not correctly calculated
for dependenci
Use new ScmProviderRepository.setPersistCheckout flag
-
Key: MRELEASE-76
URL: http://jira.codehaus.org/browse/MRELEASE-76
Project: Maven 2.x Release Plugin
Type: Improvement
Reporter: Mike Perham
This is need
[ http://jira.codehaus.org/browse/MPDASHBOARD-33?page=comments#action_56825
]
Carlos Sanchez commented on MPDASHBOARD-33:
---
I agree, it can be included in 1.1
> Change location of checkstyle files after releasing checkstyle plugin 3.0
> ---
Last time I checked the the scm plugin used code from the release plugin
- the "release:transform" taglib.
That's why I said 'move used classes to SCM plugin'.
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Lukas Theussl wrote:
Carlos Sanchez wrote:
cruisecontrol: worked last time I tried it and I believe people use
it, and it's referenced by Vincent's book.
That means you take over maintanance? ;) There are 14 issues open for it
in Jira and someone has to go through them. Here is a quote from
I was just pointing out some info to take a better decision, let me update then
cruisecontrol: +1
release: if that functionality is moved to other place +1
repository: create-upload-bundle is used in the docs to create uploads
to ibiblio, not sure if it's in that plugin or not, but that
functionali
Carlos Sanchez wrote:
cruisecontrol: worked last time I tried it and I believe people use
it, and it's referenced by Vincent's book.
That means you take over maintanance? ;) There are 14 issues open for it
in Jira and someone has to go through them. Here is a quote from Brett,
replying to a
Stephen Duncan wrote:
As I'm sure you've seen from messages on the list, this wiki has been
updated by somebody a lot recently (myself, I only added a minor fix
to a page after seeing all the notifications come in). Have you got a
plan to get the iinformation on this wiki moved to the "Space"?
cruisecontrol: worked last time I tried it and I believe people use
it, and it's referenced by Vincent's book.
release: it was used for release:prepare and release:perfrom
repository: if upload-bundle is not create-upload-bundle i'm +1
+1 for everything else
On 1/24/06, Lukas Theussl <[EMAIL PROT
Hello again,
We have discussed this before somewhat superficially but never got to a
concrete conclusion so I'd like to call for a formal vote to finalize
this and collect some opinions if necessary. Let me point out and
emphasize that we are quite short of manpower for m1, so the main
motivat
[ http://jira.codehaus.org/browse/MAVENUPLOAD-697?page=all ]
Carlos Sanchez closed MAVENUPLOAD-697:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Thanks for pointing that out
> Upload MantaRay to Maven Repository
>
1 - 100 of 216 matches
Mail list logo
