The project moved out of shared and plugins after the last release,
hence the url differences. The sites should be at
maven.a.o/enforcer/enforcer-api and enforcer-rules and the enforcer
plugin site should be in the normal plugins page. Thanks for fixing that
up...I got put off by the site plugin su
This is mostly for Brian I guess...
I'm going through the site to make sure everything is connected and
looking as slick as possible. There is one this that I don't quite
understand about the deployment of the sites though.
The currently deployed site for Enforcer looks like this:
Enforcer
BTW, the new maven-artifact api kicks ass, so much easier to use
IMO... :-)
--jason
On May 16, 2008, at 9:40 PM, Jason van Zyl wrote:
I've removed the retrotranslation from maven-artifact and deployed a
snapshot so give that a whirl.
On 16-May-08, at 4:44 AM, Jason Dillon wrote:
Hi folk
Hello,
many thread on this list makes proposal for some changes in the POM.xml
format, to be included in 4.1.0 modelVersion.
Could we use XML namespaces to support progressive enhancements ? Based on
this, proposal for new features could be added to maven, using an
to support the new schema, wit
I added a proposal for some profile activation/deactivation improvements here:
http://docs.codehaus.org/display/MAVENUSER/Improvements+to+Profile+Activation+Deactivation
Please take a look and add comments if you are interested.
Thanks!
Paul Gier wrote:
I would like to bring up a couple of is
Did you commit this to svn, I don't see any changes...
--jason
On May 16, 2008, at 9:40 PM, Jason van Zyl wrote:
I've removed the retrotranslation from maven-artifact and deployed a
snapshot so give that a whirl.
On 16-May-08, at 4:44 AM, Jason Dillon wrote:
Hi folks, can we change the ma
On May 16, 2008, at 1:29 PM, Xavier Le Vourch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Bentmann wrote:
| Daniel Kulp wrote:
|
|> Can I ask if you have anything else you think is needed before
doing
|> a release?
|
| I just closed MPMD-64 which was the only unresolved i
Hi,
The filtering of webResources in the war plugin is seriously borked (
see here [1] for a bug report back from Nov 2007 and here [2] for a
discussion on the users list just from today).
This should be fixed before a new version is released (IMHO).
-Tim
[1] http://jira.codehaus.org/browse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Bentmann wrote:
| Daniel Kulp wrote:
|
|> Can I ask if you have anything else you think is needed before doing
|> a release?
|
| I just closed MPMD-64 which was the only unresolved issue scheduled for
| 2.4. If nobody else wants to stuff thi
On Tue, May 13, 2008 at 10:08 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> In the preparation of the Maven Invoker Plugin release, I would like
> to release maven-invoker:2.0.8.
> One issue has been fixed. As there isn't a dedicated jira project a
> changes report is available here [1].
>
>
On Fri, May 9, 2008 at 1:38 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> No objections.
> But currently the war plugin trunk depends on other snapshots :
> - org.apache.maven.plugins:maven-invoker-plugin:1.2-SNAPSHOT
> - org.apache.maven.shared:maven-filtering:1.0-alpha-1-SNAPSHOT
The deplo
Daniel Kulp wrote:
Can I ask if you have anything else you think is needed before doing a
release?
I just closed MPMD-64 which was the only unresolved issue scheduled for 2.4.
If nobody else wants to stuff things into the next release, I believe that's
it.
If you think it's ready, I'd be
Hi,
A pmc vote is still missing.
Thanks,
--
Olivier
2008/5/14 John Casey <[EMAIL PROTECTED]>:
> +1
>
>
> On May 13, 2008, at 1:08 PM, Olivier Lamy wrote:
>
>> Hi,
>> In the preparation of the Maven Invoker Plugin release, I would like
>> to release maven-invoker:2.0.8.
>> One issue has been fixed
ok, thanks brian.
On Fri, May 16, 2008 at 5:17 PM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> It's not ready to go yet... but I started working on it again last
> night. The requirePluginVersions rule still chokes on reports because
> the reports get injected as plugins and it causes the build to
Hi guys,
I've developed a GreaseMonkey script that colors the mails sent by SVN to
make it easier to read the diff format (inspired by a Thunderbird extension:
http://code.google.com/p/colorediffs/). As I know some of you use GMail and
potentially Firefox as well, I thought you might like trying i
It's not ready to go yet... but I started working on it again last
night. The requirePluginVersions rule still chokes on reports because
the reports get injected as plugins and it causes the build to fail.
I'll finish this up and then do the release.
-Original Message-
From: Brett Porter [
Benjamin,
I noticed you did quite a bit of work on the PMD plugin about a month
ago.Can I ask if you have anything else you think is needed before
doing a release?
I have a couple of folks that need some of the stuff in the newer
PMD. Also, the latest PMD plugin for eclipse generate
Can you give me until tomorrow to fix the site?
Arnaud HERITIER wrote:
ok I'm taking the lead.
I'll launch the process this evening.
Arnaud
On Fri, May 16, 2008 at 2:51 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
Please do, I flipped on requirePluginVersions again today and was surprised
it
I've removed the retrotranslation from maven-artifact and deployed a
snapshot so give that a whirl.
On 16-May-08, at 4:44 AM, Jason Dillon wrote:
Hi folks, can we change the maven-artifact 3.0 bits to _attach_
instead of _replace_ when retrotranslating? I'm consuming 3.0 for
GShell, which
I agree, I think the best option for 2.0.x is to keep the current profile
behaviour, with the working profile deactivation.
I like the idea of being able to use "+myProfile" to add a profile without
deactivating the deafault profiles. But for 2.0.x I think we should just leave
the current behav
I recently upgraded from maven 2.0.8 to 2.0.9 and the
commons-build-plugin[1][2] - which is an Ant plugin - failed with the
following error
INFO]
[INFO] Building Commons JNet
[INFO]task-segment: [commons:sandbox-jira-page
ok I'm taking the lead.
I'll launch the process this evening.
Arnaud
On Fri, May 16, 2008 at 2:51 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Please do, I flipped on requirePluginVersions again today and was surprised
> it still wasn't in a release :)
>
> - Brett
>
>
> On 16/05/2008, at 6:27 P
Please do, I flipped on requirePluginVersions again today and was
surprised it still wasn't in a release :)
- Brett
On 16/05/2008, at 6:27 PM, Arnaud HERITIER wrote:
Hi Team,
Can we release enforcer 1.0 ?
Everything is fixed in the roadmap (
https://jira.codehaus.org/browse/MENFORCER?repo
+1
We allready discussed to make maven 2.1 require java5, sot it's dependencies
should also use java5. maven 2.0.x branch could then use retrotranslated
versions.
2008/5/16 Jason Dillon <[EMAIL PROTECTED]>:
> Hi folks, can we change the maven-artifact 3.0 bits to _attach_ instead of
> _replace_
Hi folks, can we change the maven-artifact 3.0 bits to _attach_
instead of _replace_ when retrotranslating? I'm consuming 3.0 for
GShell, which already requires Java 5, so the retrotranslation just
tacks on ~600k of stuff that I don't really need.
I'd like to just use the pure Java5 versio
Eh, seems like a simple fix as its only documentation.
I'd like to see 1.0 out, or perhaps a 1.0-rc-1 ASAP... regardless of
the documentation issues.
--jason
On May 16, 2008, at 4:36 PM, Jerome Lacoste wrote:
On Fri, May 16, 2008 at 10:27 AM, Arnaud HERITIER
<[EMAIL PROTECTED]> wrote:
H
On Fri, May 16, 2008 at 10:27 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi Team,
>
> Can we release enforcer 1.0 ?
> Everything is fixed in the roadmap (
> https://jira.codehaus.org/browse/MENFORCER?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
> and it fixes several impor
Let's release it !
2008/5/16 Arnaud HERITIER <[EMAIL PROTECTED]>:
> Hi Team,
>
> Can we release enforcer 1.0 ?
> Everything is fixed in the roadmap (
>
> https://jira.codehaus.org/browse/MENFORCER?report=com.atlassian.jira.plugin.system.project:roadmap-panel
> )
> and it fixes several important
Hi Team,
Can we release enforcer 1.0 ?
Everything is fixed in the roadmap (
https://jira.codehaus.org/browse/MENFORCER?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
and it fixes several important issues like MENFORCER-11 & 12.
If nobody have the time to do it, I can.
Arnaud
29 matches
Mail list logo
