Hi,
This is for those interested Maven, M2Eclipse, Nexus and how these
will all work together, and how they will work with OSGi. I'll be
talking about them at the JavaWug this Wednesday in London:
http://www.jroller.com/javawug/entry/javawug_bof_49_maven_3
It will be very much like the Mav
On 13-Jun-09, at 7:21 AM, Olivier Lamy wrote:
Hi,
It sounds good to remove link between core and doxia..
What is your idea ?
Creating a new plugin ? Moving logic to the site plugin ? Move logic
to maven-reporting-impl or something new ?
I would just encapsulate it all in the maven-site-plugin
On Sat, Jun 13, 2009 at 8:06 PM, Vincent
Siveton wrote:
> 2009/6/13 Barrie Treloar :
> The differences are mainly about links.
> See this MPIR staging page [1] vs final [2]
But that's a bug in the site plugin, right? It _ought_ to be the same
content from stage-deploy and deploy.
--
Wendy
---
On Sun, Jun 14, 2009 at 12:36 PM, Vincent
Siveton wrote:
> Yes site deploy could fail as described in 7a.
> But since the content is not the same, I recommend you to use site and
> not copy dir.
>
> Cheers,
>
> Vincent
>
> [1]
> http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.1
Hi Barrie,
2009/6/13 Barrie Treloar :
>> IMHO it is not the correct solution: mvn site:deploy and mvn
>> site:stage-deploy have different behaviours.
>
> Can you explain the differences?
> They generate the same content right?
The differences are mainly about links.
See this MPIR staging page [1]
done
On 14/06/2009, at 8:45 AM, Barrie Treloar wrote:
The Maven Eclipse Plugin has been released.
Can this get added to the next board report please.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional co
The Maven Eclipse Plugin has been released.
Can this get added to the next board report please.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.7
This plugin is used to generate Eclipse IDE files (*.classpath,
*.wtpmodules and the .settings folder) for use with a project.
http://maven.apache.org/plugins/maven-eclipse-plugin/
You should specify the v
On Sun, Jun 14, 2009 at 12:09 AM, Vincent
Siveton wrote:
> Hi Barrie,
>
> 2009/6/13 Barrie Treloar :
>> So instead of re-running this couldn't I just copy the already
>> deployed version in /www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z
>> to /www/maven.apache.org/plugins/maven-XXX-plugin ?
>
>
Hi Barrie,
2009/6/13 Barrie Treloar :
> So instead of re-running this couldn't I just copy the already
> deployed version in /www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z
> to /www/maven.apache.org/plugins/maven-XXX-plugin ?
IMHO it is not the correct solution: mvn site:deploy and mvn
site:s
On Sat, Jun 13, 2009 at 5:49 AM, Barrie Treloar wrote:
> But isn't the output of these the same content?
> So instead of re-running this couldn't I just copy the already
> deployed version in /www/maven.apache.org/plugins/maven-XXX-plugin-Y.Z
> to /www/maven.apache.org/plugins/maven-XXX-plugin ?
It's what I do. I log on people.apache.org, I remove the old site and copy
the new one
Arnaud
On Sat, Jun 13, 2009 at 2:49 PM, Barrie Treloar wrote:
> 11. Deploy the current website
>
> Note: Be sure to generate and deploy the site using the same version
> of the release. Typically, you need to
11. Deploy the current website
Note: Be sure to generate and deploy the site using the same version
of the release. Typically, you need to check out the tag (or go to
target/checkout)
cd target\checkout
mvn site-deploy -Preporting
7. Stage the latest documentation
The plugin parent POM is confi
Hi,
The vote has passed with the following result :
+1 (binding): Benjamin Bentmann, Arnaud Heritier, Olivier Lamy
+1 (non binding): Nicolas Deloof, Barrie Treloar
I will promote the artifacts to the central repo.
-
To unsubscri
14 matches
Mail list logo
