Hi all,
I don't know if my vote would still count, but here is my +1 anyways -
Petar is a very dedicated person, and have been worked closely to
Maven since he ported Cactus build to Maven 2.
-- Felipe
On Mon, Jan 12, 2009 at 9:10 AM, John Casey wrote:
> [x] +1, sounds good
-
Dion Gillard wrote:
In this context, I'd call 1.1 beta 2 a 'Stable' release. People are
definitely using it as such. It's (in my mind anyways), v1.1.0.
Since Maven is nothing without the plugins, upgrading those is reason enough
for a new release (1.1.1).
Thoughts?
I'm a +1 - even though our
Hi all,
Is it posible to remove/replace a file from the generated M2 artifact
after the test phase (but before install)?
Let me try to explain my case to make it clear: I have a Struts-based
web application built with Maven 2 which depends on some DAO interfaces
defined in another project. D
Hi Brett, Jason and others,
I'm trying to set up MRM at work and I'd like a little help, as there
is no documentation about it yet.
Right now, I was able to modify plexus.xml, generate and deploy the
war, and create some directories on /tmp/MRM (which is the path I've
chosen on plexus.xml). Now,
Hi Brett,
I've just tried to build it, and got the same issue (out of the box :-(
BTW, is there a web page for the MRM yet?
[]s,
-- Felipe
On 3/31/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> It requires 2.1-SNAPSHOT of the jar plugin fro the jar:sign goal. I've
> deployed a new snapshot -
[ http://jira.codehaus.org/browse/MPRAR-1?page=comments#action_57253 ]
Felipe Leme commented on MPRAR-1:
-
Stephane,
Could you please add a small test case for this issue (and also MPRAR-2)? I
know the rar plugin does not have any testcase yet, but you
Oops, forgot to mention the link for the forum:
https://sourceforge.net/forum/forum.php?thread_id=1423018&forum_id=373867
More specifically, the questions are in this reply:
https://sourceforge.net/forum/message.php?msg_id=3528229
-- Felipe
Felipe Leme wrote:
We still have some quest
Hi again,
We still have some questions, like where is the Maven public key. So,
could you please join the forum and help us out? Once we (emma) suceed,
we (maven :-) could publish a how-to on Maven's site explaining the
process (as Brian mentioned in an earlier message, that would help a lot
Ok, I will see if sourceforge can provide it.
Just another question: must it have a maven2 layout with the rewrite
rules or a maven1 layout is fine?
Thanks again,
-- Felipe
Carlos Sanchez wrote:
They need a ssh accessible server with their repo and add the maven
public key (which is availa
[ http://jira.codehaus.org/browse/MPECLIPSE-84?page=all ]
Felipe Leme closed MPECLIPSE-84:
Resolution: Fixed
Fix Version: 1.11
Fixed, by creating the maven.eclipse.project.name, which is more generic than
simply adding a prefix (see my
Brett/Carlos (and others :-),
Is there a policy where a 3rd party open source project could
automaticaly synchronize their jars into ibiblio (without having to
submit a MAVENUPLOAD request)? The interested party in this case is the
emma project:
https://sourceforge.net/forum/message.php?msg_
Brett,
Is the browsing going to be fixed? I mean, browsing 'by humans' is
important as well...
-- Felipe
Brett Porter wrote:
It's just browsing that is disabled. Doesn't going direct to the
artifact work?
-
To unsubscri
Brett Porter wrote:
Would you mind sending some details out to that list? I am not
subscribed so I can't get to the archives.
Neither am I, actually :-(
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
BTW, when these rewrite rules were created, were the ibiblio admins been
notified on the changes?
I'm asking because we mirrors ibiblio at work and the guy responsible
for the job wasn't aware of the change, even though he is subscribed to
the ibiblio-mirrors list
(http://lists.ibiblio.org/ma
Create property to disable compilation warning
--
Key: MPJAVA-44
URL: http://jira.codehaus.org/browse/MPJAVA-44
Project: maven-java-plugin
Type: New Feature
Versions: 1.5
Reporter: Felipe Leme
Priority
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Heh, that's interesting. I'll put a rule in for that one specifically.
That would be great.
Anyways, I''ve also found another glitch:
http://ibiblio.org/maven/jaxen/jars/jaxen-1.0-FCS-full.jar
points to:
http://ibiblio.org/maven2/jaxen/
On 1/9/06, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> Heh, that's interesting. I'll put a rule in for that one specifically.
That would be great.
Anyways, I''ve also found another glitch:
http://ibiblio.org/maven/jaxen/jars/jaxen-1.0-FCS-full.jar
points to:
http://ibiblio.org/maven2/jaxen/
Weird, it was screwed a couple of minutes ago (the
http://www.ibiblio.org/maven was redirecting to the
http://www.ibiblio.org/maven/public/html/maven, which in turn didn't have
any groupId dir)...
-- Felipe
On 1/9/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>
> http://www.ibiblio.org/maven
Hi Brett,
Sorry for the stupid question (I haven't been following the lists for a
while), but where is the old repo right now? My maven1 projects are failing
because the http://www.ibiblio.org/maven/public/html/maven/ only have 2
sub-dires, maven and poms...
-- Felipe
On 1/8/06, Brett Porter <[
[
http://jira.codehaus.org/browse/MPANNOUNCEMENT-5?page=comments#action_50318 ]
Felipe Leme commented on MPANNOUNCEMENT-5:
--
Gary,
Do you mean the message should have an tag pointing to the issue, as
it happens on the changes-reports.html?
If so
[ http://jira.codehaus.org/browse/MPANNOUNCEMENT-19?page=all ]
Felipe Leme closed MPANNOUNCEMENT-19:
-
Resolution: Fixed
> Failing when the version is missing should be optio
[
http://jira.codehaus.org/browse/MPANNOUNCEMENT-19?page=comments#action_50310 ]
Felipe Leme commented on MPANNOUNCEMENT-19:
---
On a second thought, there are more places where those restrictions should be
ignored - for instance, if the project
Reporter: Felipe Leme
Assigned to: Felipe Leme
Fix For: 1.4
The announcement goal fails if the current version is not added on the
element. Although this is nice, sometimes it might not be convenient
(for instance, you might have a project made of several sub-projects and you
would
[ http://jira.codehaus.org/browse/MPGENAPP-3?page=all ]
Felipe Leme closed MPGENAPP-3:
--
Resolution: Fixed
Closed.
Note though that I used the maven.genapp.basedir.prompt and
maven.genapp.basedir as properties (sorry, I had used those properties while
[ http://jira.codehaus.org/browse/MPGENAPP-10?page=all ]
Felipe Leme closed MPGENAPP-10:
---
Resolution: Fixed
Fix Version: 2.3
Fixed.
Note though that the dependencies are a bit older; for instance, it's using
xdoclet 1.2 (instead of 1.2.3
[ http://jira.codehaus.org/browse/MPGENAPP-15?page=comments#action_49436 ]
Felipe Leme commented on MPGENAPP-15:
-
MPECLIPSE-34 has been marked as incomplete; should we do the same with this
issue as well?
> Eclipse plugin templ
maven.javadoc.customtags cannot handle dashes (-)
-
Key: MPJAVADOC-62
URL: http://jira.codehaus.org/browse/MPJAVADOC-62
Project: maven-javadoc-plugin
Type: Bug
Versions: 1.7
Reporter: Felipe Leme
Due to that
[ http://jira.codehaus.org/browse/MPGENAPP-17?page=all ]
Felipe Leme closed MPGENAPP-17:
---
Assign To: Felipe Leme
Resolution: Fixed
Fix Version: 2.3
Added test case and fix it.
> Incorrectly assumes user's .maven directory is ${u
[ http://jira.codehaus.org/browse/MPGENAPP-23?page=all ]
Felipe Leme closed MPGENAPP-23:
---
Assign To: Felipe Leme
Resolution: Fixed
Fix Version: 2.3
Fixed, by using maven.genapp.repackage.dir instead of hardcoded 'src'.
&
[ http://jira.codehaus.org/browse/MPGENAPP-24?page=comments#action_49260 ]
Felipe Leme commented on MPGENAPP-24:
-
Hi again,
I tried to set the properties to skip the prompt, but it didn't work, I mean,
not all the questions were skipped; I wil
[ http://jira.codehaus.org/browse/MPGENAPP-24?page=comments#action_49257 ]
Felipe Leme commented on MPGENAPP-24:
-
Arnauld,
I have createad a class that sets the System.in to always return enter:
package org.apache.maven.genapp.testing;
import
[ http://jira.codehaus.org/browse/MPGENAPP-24?page=comments#action_49207 ]
Felipe Leme commented on MPGENAPP-24:
-
Hi Arnauld,
Well, at least after months of inactivity I contributed with something useful
:-)
Now we just need to figure it out an
[ http://jira.codehaus.org/browse/MPGENAPP-24?page=all ]
Felipe Leme closed MPGENAPP-24:
---
Resolution: Fixed
Fixed.
PS: I added a test case, although the test case interactes with the user (which
is bad :-(.
> Allow project to be genera
Leme
Assigned to: Felipe Leme
Priority: Minor
Fix For: 2.3
When you run genapp, it creates the new project in the current directory. I see
at least one situation (which is why I'm creating this issue) where that is not
desired: when creating test cases for this plugin!
So, I
Hi Brett,
Brett Porter wrote:
That doc hasn't been on the main site for a long time and should be
removed.
See, Google makes some documents immortal :-)
Maven 1.0 is available under the link at the top of the page. We're
Sorry, I should have tried it again before sending my previous mess
Hi Jason,
Now that the move is done, what about the /maven1 directory?
The way the site is now, you cannot browse to the old maven1 stuff; in
particular, I had to find that user guide I had to use Google to help me:
http://maven.apache.org/reference/user-guide.html
-- Felipe
Jason van Zyl
The cactus team is pleased to announce the Maven Cactus plugin 1.7.1
release!
http://jakarta.apache.org/cactus/integration/maven/
Maven plugin for Cactus (http://jakarta.apache.org/cactus) that allows to
automatically start containers, run Cactus tests and stop the containers.
Changes in this ve
[ http://jira.codehaus.org/browse/MPECLIPSE-84?page=comments#action_43539 ]
Felipe Leme commented on MPECLIPSE-84:
--
Joakin,
What about this:
1.Instead of setting maven.eclipse.project.prefix=B32, every developer set
something like: mycompany.prefix
[ http://jira.codehaus.org/browse/MPECLIPSE-84?page=comments#action_43458 ]
Felipe Leme commented on MPECLIPSE-84:
--
Joakin,
Rather than providing a prefix, we should use a property for the whole name;
something like this:
on plugin.properties
[ http://jira.codehaus.org/browse/MPECLIPSE-70?page=comments#action_43267 ]
Felipe Leme commented on MPECLIPSE-70:
--
Eric/Brett,
I found another use case wher this customization is useful: when doing expanded
deploy on JBoss (or other application
Brett Porter wrote:
Can we give Carlos commit access to that until the infra is properly set
up? With any luck, he'll fix a few Maven 1.1 core bugs while he is at it :)
I don't think my vote is binding, but here is the +1 anyway...
-
Site is lacking changes-report and announcments for 1.5 release
---
Key: MPSCM-57
URL: http://jira.codehaus.org/browse/MPSCM-57
Project: maven-scm-plugin
Type: Bug
Versions: 1.5
Reporter: Felipe
Brett Porter wrote:
A single +1 indicates agreement to all of the below. Otherwise, please
+1 - I don't use any of them neither and I believe/agree what you said.
(my only exception would be Jira maybe - I used it a couple of months
ago and it seemed to be working fine, so I'm +0 for this on
Brett Porter wrote:
+1 from me.
Me too.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MPARTIFACT-18?page=comments#action_40739
]
Felipe Leme commented on MPARTIFACT-18:
---
Vijay,
The patches are attached in this very issue. See attachments section above or
try the following link:
http
On Mon, 2005-06-06 at 13:35 +1000, Brett Porter wrote:
> Isn't that how the instructions are?
>
> plugin:repository-deploy,site:deploy,site:publish
No, the site only says:
Produce a clean build using maven -Dmaven.repo.list=apache scm:perform-
release. When prompted for the tag, enter the one us
On Mon, 2005-06-06 at 13:24 +1000, Brett Porter wrote:
> That's not the standard way to do things... site:publish is meant to
> push it live from staging, so that both sites are updated.
So, how should we do the releases then? I mean the maven plugins
project, not a generic project using maven..
The maven team is pleased to announce the Maven EAR Plugin 1.7 release!
http://maven.apache.org/reference/plugins/ear/
Ear Plugin for Maven
Changes in this version include:
New Features:
o Added property maven.ear.final.name. Issue: MPEAR-25.
Fixed bugs:
o Improved how dependencies are c
On Mon, 2005-06-06 at 13:00 +1000, Brett Porter wrote:
> >http://maven.apache.org/developers/making-releases.html
> >
> >Shouldn't this property/procedure be described there?
> >
> >
> No, they are only a workaround because of permission issues. Like I
> said, I think it -did- work the first ti
On Mon, 2005-06-06 at 11:54 +1000, Brett Porter wrote:
> As before, you can use -Dmaven.site.deploy.live=true to push directly
Hmm, I followed these instructions:
http://maven.apache.org/developers/making-releases.html
Shouldn't this property/procedure be described there?
> You can probably ch
peration
not permitted (1)
[exec] rsync error: some files could not be transferred (code 23) at
main.c(702)
[exec] [ERROR] Result: 23
-- Felipe
On Mon, 2005-05-30 at 21:55 +1000, Brett Porter wrote:
> Felipe Leme wrote:
>
> >Hmm, when I released the EAR plugin a couple of we
On Mon, 2005-06-06 at 07:34 +1000, Brett Porter wrote:
> Sounds more like a 1.6.2 to me, but +1.
I think 1.7 is better, as it introduces a new property.
-- Felipe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
Hi all,
Copying & pasting Vince's last messages, I'd like to release the EAR
plugin before the Maven 1.1 final release (i.e.real soon).
Is that ok with everyone?
Here's my +1
Disclaimer: the goal here is not fix outstanding issues but rather to
have a release of the plugin for the Maven 1.1 rel
On Sat, 2005-06-04 at 14:40 +0200, Vincent Massol wrote:
> Is that ok with everyone?
Yes.
> Here's my +1
And here's mine...
-- Felipe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTEC
On Sat, 2005-06-04 at 14:38 +0200, Vincent Massol wrote:
> Is that ok with everyone?
+1
(I was going to add the issueId for MPJAR-38, but you have already done
it :-)
-- Felipe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On Fri, 2005-06-03 at 17:03 +1000, Brett Porter wrote:
> Given those assumptions, please vote on this.
++ 1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, 2005-06-03 at 09:19 +1000, Brett Porter wrote:
> From me, +1.
Me too...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
: Improvement
Versions: 1.5
Reporter: Felipe Leme
Right now the java:compile task includes everything (except .html files):
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
On Thu, 2005-06-02 at 11:22 +1000, Brett Porter wrote:
> [X] +1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Mon, 30 May 2005 21:55:46 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> I did, but I didn't have the problem before either.
It's fine then.
> Can you elaborate?
Sorry, but I don't remember what it was and I was in a hurry at that time so I
just used beta3. But I "sense" it's fixed now.
On Mon, 2005-05-30 at 10:17 +0200, Arnaud HERITIER wrote:
> Wasn't there a problem with the RC1 ?
> I remember that the last time I used it to release a plugin, I need to use
> the beta 3 that Vincent sent to me ?
Hmm, when I released the EAR plugin a couple of weeks ago, I think (but
not sur
Hi Brett,
Yes, I know, but I'm not subscribed there and didn't want to just
subscribe and out of the blue send such message (anyway, I thought many
developers were maven committers too).
-- Felipe
On Fri, 2005-05-20 at 10:52 +1000, Brett Porter wrote:
> Please send this to commons-dev. Most of
Hi all,
I had submitted some Jelly patches a couple of weeks ago, but didn't get
any comments about them
http://issues.apache.org/jira/browse/JELLY-194
http://issues.apache.org/jira/browse/JELLY-203
http://issues.apache.org/jira/browse/JELLY-204
http://issues.apache.org/jira/browse/JELLY-205
E
On Tue, 2005-05-17 at 07:19 +1000, Brett Porter wrote:
> Can you explain your use case, and would adding the 1 - 3 lines in each
> pom be prohibitive?
It would not be prohibitive, but imagine I have dozens of projects whose
default goal is the same (defined in a custom plugin, for instance). It
wo
[ http://jira.codehaus.org/browse/MAVEN-256?page=all ]
Felipe Leme updated MAVEN-256:
--
Attachment: head.patch
Patch similar to the previous one, but this time diffed against the HEAD branch.
> does not use the global sess
[ http://jira.codehaus.org/browse/MAVEN-256?page=all ]
Felipe Leme updated MAVEN-256:
--
Attachment: 1.0.2.patch
I'm providing a patch that creates a HashMap on the JellyContext and makes sure
a goal is executed only once (either on attainGoal or as pr
Me too...
On Mon, 2005-05-16 at 09:15 -0700, dan tran wrote:
> In M1, I heavily use default goal inheritant.This way I dont have to add an
> extra maven.xml to all sub probject.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
[ http://jira.codehaus.org/browse/MAVEN-1606?page=comments#action_39143 ]
Felipe Leme commented on MAVEN-1606:
PS: I guess the culprit is the following resource:
plugin.jelly
plugin.properties
NPE when using maven-tasks-plugin 1.2.0
---
Key: MAVEN-1606
URL: http://jira.codehaus.org/browse/MAVEN-1606
Project: maven
Type: Bug
Components: core
Versions: 1.1-beta-2
Reporter: Felipe Leme
Priority: Blocker
On Mon, 2005-05-16 at 20:17 +1000, Brett Porter wrote:
> inside . Not inherited. Specifies the goal to use
> if none is specified.
Why not inherited?
-- Felipe
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
[ http://jira.codehaus.org/browse/MAVEN-1294?page=comments#action_39133 ]
Felipe Leme commented on MAVEN-1294:
Brett,
Why wouldn't it work? I mean, I was planning to change a local Maven 1.0.2
installation to Jelly 1.0 in order to fix this
[ http://jira.codehaus.org/browse/MJT-5?page=all ]
Felipe Leme updated MJT-5:
--
Attachment: MJT5-metadata.patch
Changes on project.xml and xdocs/changes.xml
> [PATCH] New tag
> ---
>
> Key: MJT-5
>
[PATCH] New tag
---
Key: MJT-5
URL: http://jira.codehaus.org/browse/MJT-5
Project: maven-jelly-tags
Type: New Feature
Versions: 1.0
Reporter: Felipe Leme
Fix For: 1.1
Attachments: GetTag.patch
We have a tag that can be
list about the
process and got this answer:
On Fri, 2004-11-19 at 10:51 +0100, Vincent Massol wrote:
>
> > -Original Message-
> > From: Felipe Leme [mailto:[EMAIL PROTECTED]
> >
> > So, what's the procedure? Is it necessary to ask for a vote (I've s
The maven team is pleased to announce the Maven EJB Plugin 1.6 release!
http://maven.apache.org/reference/plugins/ejb/
EJB Plugin for Maven
Changes in this version include:
New Features:
o Added new maven.ejb.build.dir property that specifies the location
where the EJBs are generated.
Cha
Hi all,
I've been trying to release maven-ejb-plugin 1.6 (which is a requirement
for the upcoming Cactus 1.7.1), but been facing a lot of issues. I've
already managed to install the proper versions of site and scm plugins,
but now I got an error regarding JCE:
Deploying to repository: apache
JCE
[ http://jira.codehaus.org/browse/MPWAR-30?page=comments#action_38310 ]
Felipe Leme commented on MPWAR-30:
--
Hi Fabrizio,
The problem with adding jar:jar as prereqs is that it would be called anyway,
even if the project does not have any Java file
[ http://jira.codehaus.org/browse/MPWAR-30?page=comments#action_38219 ]
Felipe Leme commented on MPWAR-30:
--
I was going to mark this as "Won't Fix" because it kind of goes against Maven
way of doing thing (in other words, there should b
On Tue, 2005-04-12 at 00:22 +1000, Brett Porter wrote:
> [x] +1, go for it
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Tue, 2005-04-05 at 18:00 +0200, Vincent Massol wrote:
> I feel a bit like Eric which is why I've not answered to the vote so far
> (I'm still unsure whether it's a good idea or not).
I'm in the same situation :-)
> - rough planning for m2. First alpha, first beta, planned 1.0 and their
> con
[
http://jira.codehaus.org/browse/MPHIBERNATE-14?page=comments#action_31491 ]
Felipe Leme commented on MPHIBERNATE-14:
Dan,
Unfortunately, the fix is not that simple, as such change would cease the
support to Hibernate 2.x.
In other words
[ http://jira.codehaus.org/browse/MPECLIPSE-81?page=comments#action_30898 ]
Felipe Leme commented on MPECLIPSE-81:
--
PS: in the last paragraph I meant the test resources...
> Resources are added as path even if they do not exist in the filesys
: 1.9
Reporter: Felipe Leme
If the property maven.eclipse.resources.addtoclasspath is set to true and the
resources directory is defined in the POM but does not exist in the filesystem,
the generated .classpath will cause Eclipse to fail.
A quick fix is to just put an at classpath.jelly
[ http://jira.codehaus.org/browse/MPEAR-38?page=history ]
Felipe Leme closed MPEAR-38:
Resolution: Duplicate
> maven.ear.appxml is not used correctly
> --
>
> Key: MPEAR-38
>
[ http://jira.codehaus.org/browse/MPEAR-38?page=history ]
Felipe Leme reopened MPEAR-38:
--
Reopening because I closed with the wrong resolution...
> maven.ear.appxml is not used correctly
> --
>
> K
[ http://jira.codehaus.org/browse/MPEAR-38?page=history ]
Felipe Leme closed MPEAR-38:
Fix Version: 1.6
Resolution: Fixed
Assign To: Felipe Leme
This code was already changed when fixing MPEAR-24:
# svn diff -r 116236 plugin.jelly
[ http://jira.codehaus.org/browse/MPEAR-39?page=history ]
Felipe Leme closed MPEAR-39:
Resolution: Fixed
> Improve algorithm that copies the bundled dependencies
> --
>
> K
[ http://jira.codehaus.org/browse/MPJAVA-8?page=comments#action_30704 ]
Felipe Leme commented on MPJAVA-8:
--
PS: here is a thread where this issue was discussed:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=905391
>
27;t think using such tag is so
trivial (I didn't even know such tag, to be honest :-(
-- Felipe
--
Felipe Leme <[EMAIL PROTECTED]>
Falcon Informática
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Improve algorithm that copies the bundled dependencies
--
Key: MPEAR-39
URL: http://jira.codehaus.org/browse/MPEAR-39
Project: maven-ear-plugin
Type: Improvement
Versions: 1.6.1
Reporter: Felipe Leme
Hi Brett,
FYI, I released maven-hibernate-plugin 1.3 using this SCM beta and it
worked fine.
-- Felipe
On Fri, 2005-01-07 at 10:49, Brett Porter wrote:
> I have a released a beta of the SCM plugin with subversion support.
> Please test this even if you are already using this plugin for CVS as
The maven team is pleased to announce the Maven Hibernate Plug-in 1.3
release!
http://maven.apache.org/reference/plugins/hibernate/
Changes in this version include:
New Features:
o Added new goal hibernate:code-generation. Issue: MPHIBERNATE-12.
Thanks to
Paul Kearney.
o Added new g
t would requires a lot of
changes in large projects).
What do you guys think?
-- Felipe
On Sun, 2004-08-01 at 18:38, Felipe Leme wrote:
> On Sat, 2004-07-31 at 11:11, Brett Porter wrote:
>
> > I was actually thinking it would be better to add an attribute to the
> > attainGoal
t would requires a lot of
changes in large projects).
What do you guys think?
-- Felipe
On Sun, 2004-08-01 at 18:38, Felipe Leme wrote:
> On Sat, 2004-07-31 at 11:11, Brett Porter wrote:
>
> > I was actually thinking it would be better to add an attribute to the
> > attainGoal
+1
On Fri, 2005-01-14 at 02:51, Brett Porter wrote:
> I'd like to propose Alex Karasulu as a committer on the Maven plugins and
> plugins sandbox.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [E
On Wed, 2005-01-05 at 11:59, Dion Gillard wrote:
> 3) ony check the artifact/types/artifact-version.type part of the
> overall file name?
Yes, that is the better approach, but a pain to implement. We would need
to take the canonical path from the full path and just the repository
and then "crop"
On Tue, 2005-01-04 at 08:45, Brett Porter wrote:
> I messed these up with an accidental kill in the middle (wrong process).
Do you mean you killed a 'svn commit' in the middle? I thought commits
were atomic on subversion (that's one of the CVS limitations subversion
is supposed to tackle), so that
The maven team is pleased to announce the Maven EAR Plugin 1.6.1
release!
http://maven.apache.org/reference/plugins/ear/
Ear Plugin for Maven
Changes in this version include:
Fixed bugs:
o Fixed path of bundled dependency on generated application.xml. Issue:
MPEAR-31.
Changes:
o
Ok, I will be releasing it over the weekend.
Meanwhile, you provided a 'pre-release' using the following command:
maven plugin:download
-Dmaven.repo.remote=http://apache.org/~felipeal/maven_repo -DgroupId=maven
-DartifactId=maven-ear-plugin -Dversion=1.6.1-SNAPSHOT
So, for those having issues
Hi all,
Due to the new bugs on the ear plugin (MPEAR-31 and MAVEN-2526/MPEAR-9), I
think we should release a new version for the plugin, as soon as we get some
confirmation from the users that the problems are fixed.
I have a question then: should it be 1.6.1 or 1.7? It is mostly a bug fix
rel
1 - 100 of 194 matches
Mail list logo
