Menu
▾
▴
maven-plugins-developer — Mailing List used for development of plugins
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(14) |
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(12) |
Sep
(14) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2004 |
Jan
(4) |
Feb
(8) |
Mar
(14) |
Apr
(18) |
May
(1) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(5) |
Oct
(26) |
Nov
(36) |
Dec
(21) |
| 2005 |
Jan
(10) |
Feb
(20) |
Mar
(15) |
Apr
(11) |
May
(29) |
Jun
(18) |
Jul
(19) |
Aug
(12) |
Sep
(11) |
Oct
(3) |
Nov
(7) |
Dec
(5) |
| 2006 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
(14) |
Jul
(45) |
Aug
(58) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2007 |
Jan
(4) |
Feb
|
Mar
|
Apr
(3) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jorn A H. <Jo...@pe...> - 2002-09-12 14:05:07
|
Hi Stephane/others, I can see you already commented on the logos in the WikiSandbox :-) Yes you are right that the root/site/reactor logo (what should we call it?) doesn't tell very much. The idea was to let the /** thing give a hint about something like "use a glob patterne for everthing below" - but maybe it's too vague? But my thought was to add something more descriptive as a replacement for the jakarta logo you have "borrowed" for the moment. That would show up omn all the pages and symbolize the identity for the whole "maven-plugins" family I have attached a couple of half-baked ideas - I think we could add all of the name "maven-plugins" somehow if you like... thoughts? The "gears" idea also sounds great - do you have something draw yet?? Should we have a vote on the logos? -Jørn |
|
From: Jorn A H. <Jo...@pe...> - 2002-09-11 22:16:14
|
Ooops, Sorry to dump that stuff on you guys. That should have gone to the jakarta-turbine-maven-developer list not maven-plugins. I really hate using this web-mail stuff :-( Sorry again, Jørn > > > > ----- Original Message ----- > > From: "Stéphane Mor" <ste...@ya...> > > > I just noticed something : the project's version is written nowhere on > > > the site !! > > > > > > Don't you think that would be a good info to provide ? [SNIP] |
|
From: Jorn A H. <Jo...@pe...> - 2002-09-11 21:45:30
|
> > ----- Original Message ----- > From: "Stéphane Mor" <ste...@ya...> > > I just noticed something : the project's version is written nowhere on > > the site !! > > > > Don't you think that would be a good info to provide ? > > Yes, that would be nice. > > I even think that you could go a step further and provide links between different "important" versions of the site. For Maven that could ATM be the B4 release, the B6 release and HEAD. > > My first attempt to a solution for this is a small patch to the xdoc plugin. Please find it attached. It relies on the user adding a <otherVersions> element to the already existing navigation.xml file like this: > > <body> > <otherVersions> > <item name="Beta-4" href="http://jakarta.apache.org/turbine/maven/BETA4/"/> > <item name="Beta-6" href="http://jakarta.apache.org/turbine/maven/"/> > <item name="Beta-7-SNAPSHOT" href="http://jakarta.apache.org/turbine/maven/SNAPSHOT/"/> > </otherVersions> > > The downside with this is that you have to apply this for every directory where you have a navigation.xml. I tried to put the info in the <versions> section of project.xml where the info really should live. That didn't work for me - so I suppose project.xml is not available in the dvsl context in the same way as the navigation.xml. > > Another problem with this is that there will be dangling links when the page structure changes between versions. But on a project with a "nice stable" structure this problem would be minor. I have no good solution for this... which when thinking about it sounds like a familiar problem for many SCM systems :-( > > A IMO Real Cool addition to all this would be the ability to mark up documentation changes as html-diffs between versions. This would help a lot of Maven users wanting to know exactly what has changed since last time they checked and I think it would be "more fun to help yourself as a user" :-) Which in turn would let developers spend more time on developing! > > Another addition would be a page history section on each page with checkin comments. > > > > > Do you think of a good place to put it ? > > With my current solution you can see the version as part of the URL for any page. I think this is simple and intuitive - but it would be trivial to ad it somewhere on the page to let it stand more out. > > Thoughts on all this? > > Thanks, > Jørn A Hansen > > ---------------------------------------------------- > Name: site.patch > Type: application/octet-stream > Encoding: base64 > Length: 1.89 KB -- Jørn A Hansen |
|
From: Jorn A H. <Jo...@pe...> - 2002-09-11 21:26:49
|
----- Original Message -----
From: "Stéphane Mor" <ste...@ya...>
> I just noticed something : the project's version is written nowhere on
> the site !!
>
> Don't you think that would be a good info to provide ?
Yes, that would be nice.
I even think that you could go a step further and provide links between different "important" versions of the site. For Maven that could ATM be the B4 release, the B6 release and HEAD.
My first attempt to a solution for this is a small patch to the xdoc plugin. Please find it attached. It relies on the user adding a <otherVersions> element to the already existing navigation.xml file like this:
<body>
<otherVersions>
<item name="Beta-4" href="http://jakarta.apache.org/turbine/maven/BETA4/"/>
<item name="Beta-6" href="http://jakarta.apache.org/turbine/maven/"/>
<item name="Beta-7-SNAPSHOT" href="http://jakarta.apache.org/turbine/maven/SNAPSHOT/"/>
</otherVersions>
The downside with this is that you have to apply this for every directory where you have a navigation.xml. I tried to put the info in the <versions> section of project.xml where the info really should live. That didn't work for me - so I suppose project.xml is not available in the dvsl context in the same way as the navigation.xml.
Another problem with this is that there will be dangling links when the page structure changes between versions. But on a project with a "nice stable" structure this problem would be minor. I have no good solution for this... which when thinking about it sounds like a familiar problem for many SCM systems :-(
A IMO Real Cool addition to all this would be the ability to mark up documentation changes as html-diffs between versions. This would help a lot of Maven users wanting to know exactly what has changed since last time they checked and I think it would be "more fun to help yourself as a user" :-) Which in turn would let developers spend more time on developing!
Another addition would be a page history section on each page with checkin comments.
>
> Do you think of a good place to put it ?
With my current solution you can see the version as part of the URL for any page. I think this is simple and intuitive - but it would be trivial to ad it somewhere on the page to let it stand more out.
Thoughts on all this?
Thanks,
Jørn A Hansen
|
|
From: <ste...@ya...> - 2002-09-10 02:26:11
|
Jorn A Hansen wrote:
Good idea !
Though, it appears that right now, the Reactor doesn't take extended
projects into account...
With the reactor, "../project.xml" is considered to be from the current
dir, ie from the top
dir.
If you set it to "${basedir}/../project.xml", it is not transformed and
throws an error.
I'll have a look at all that, and apply the patch as soon as I can
generate the site with it.
Thanks,
Stéphane
>Hi,
>
>This patch uses the <extend> inheritance mechanism which allows for easier maintenance of the Wiki and RPM project descriptors.
>
>The following elements are now inherited from the site POM:
> organization
> gumpRepositoryId
> issueTrackingUrl
> mailingLists
> build
>
>Apart from that there is a minor fix for these elements:
>- name
>- package
>
>
>Thanks,
> Jørn
>
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
|
|
From: Jorn A H. <Jo...@pe...> - 2002-09-09 21:17:39
|
Hi, This patch uses the <extend> inheritance mechanism which allows for easier maintenance of the Wiki and RPM project descriptors. The following elements are now inherited from the site POM: organization gumpRepositoryId issueTrackingUrl mailingLists build Apart from that there is a minor fix for these elements: - name - package Thanks, Jørn |
|
From: <ste...@ya...> - 2002-09-09 00:48:36
|
Patch applied! Thanks a lot! Stéphane >Hi again, > >Please ignore my previous post. For some odd reason my webmail client seems to strip the leading plus-signs from the CVS diff lines :-( > >This post contains the same patch again sent as an attachment which seems to work better... > >Sorry for the inconvenience, >Jørn A Hansen > > > >>Hi, >> >>Here is a small patch that: >>- fixes the inceptionYear >>- points the issueTrackingUrl to the SourceForge Tracker >>- and has some additions to the mailingLists section. >> >>Thanks, >>Jørn A Hansen >> >> >>Index: project.xml >>=================================================================== >>RCS file: /cvsroot/maven-plugins/maven-plugins/project.xml,v >>retrieving revision 1.11 >>diff -u -r1.11 project.xml >>--- project.xml 4 Sep 2002 22:13:18 -0000 1.11 >> project.xml 8 Sep 2002 19:14:29 -0000 >>@@ -10,7 10,7 @@ >> <url>http://jakarta.apache.org/</url> >> <logo>http://jakarta.apache.org/turbine/maven/images/jakarta-logo-blue.gif</logo> >> </organization> >>- <inceptionYear>2001</inceptionYear> >> <inceptionYear>2002</inceptionYear> >> <package>org.apache.maven.plugins</package> >> <logo>http://jakarta.apache.org/turbine/maven/images/maven.jpg</logo> >> >> > >[SNIP] > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com |
|
From: Jorn A H. <Jo...@pe...> - 2002-09-08 21:45:07
|
Hi again, Please ignore my previous post. For some odd reason my webmail client seems to strip the leading plus-signs from the CVS diff lines :-( This post contains the same patch again sent as an attachment which seems to work better... Sorry for the inconvenience, Jørn A Hansen > Hi, > > Here is a small patch that: > - fixes the inceptionYear > - points the issueTrackingUrl to the SourceForge Tracker > - and has some additions to the mailingLists section. > > Thanks, > Jørn A Hansen > > > Index: project.xml > =================================================================== > RCS file: /cvsroot/maven-plugins/maven-plugins/project.xml,v > retrieving revision 1.11 > diff -u -r1.11 project.xml > --- project.xml 4 Sep 2002 22:13:18 -0000 1.11 > project.xml 8 Sep 2002 19:14:29 -0000 > @@ -10,7 10,7 @@ > <url>http://jakarta.apache.org/</url> > <logo>http://jakarta.apache.org/turbine/maven/images/jakarta-logo-blue.gif</logo> > </organization> > - <inceptionYear>2001</inceptionYear> > <inceptionYear>2002</inceptionYear> > <package>org.apache.maven.plugins</package> > <logo>http://jakarta.apache.org/turbine/maven/images/maven.jpg</logo> [SNIP] |
|
From: Jorn A H. <Jo...@pe...> - 2002-09-08 21:21:47
|
Hi,
Here is a small patch that:
- fixes the inceptionYear
- points the issueTrackingUrl to the SourceForge Tracker
- and has some additions to the mailingLists section.
Thanks,
Jørn A Hansen
Index: project.xml
===================================================================
RCS file: /cvsroot/maven-plugins/maven-plugins/project.xml,v
retrieving revision 1.11
diff -u -r1.11 project.xml
--- project.xml 4 Sep 2002 22:13:18 -0000 1.11
project.xml 8 Sep 2002 19:14:29 -0000
@@ -10,7 10,7 @@
<url>http://jakarta.apache.org/</url>
<logo>http://jakarta.apache.org/turbine/maven/images/jakarta-logo-blue.gif</logo>
</organization>
- <inceptionYear>2001</inceptionYear>
<inceptionYear>2002</inceptionYear>
<package>org.apache.maven.plugins</package>
<logo>http://jakarta.apache.org/turbine/maven/images/maven.jpg</logo>
@@ -23,7 23,7 @@
<shortDescription>Collection of plugins for Apache Jakarta Maven</shortDescription>
<url>http://${pom.id}.sourceforge.net</url>
- <issueTrackingUrl>http://nagoya.apache.org/scarab/servlet/scarab/</issueTrackingUrl>
<issueTrackingUrl>http://sourceforge.net/tracker/?group_id=61626</issueTrackingUrl>
<siteAddress>${pom.id}.sourceforge.net</siteAddress>
<siteDirectory>/home/groups/${pom.id.substring(0,1)}/${pom.id.substring(0,2)}/${pom.id}/htdocs/</siteDirectory>
<distributionDirectory>/home/groups/${pom.id.substring(0,1)}/${pom.id.substring(0,2)}/${pom.id}/htdocs/distributions/</distributionDirectory>
@@ -44,11 44,19 @@
<name>Maven-Plugins User List</name>
<subscribe>${pom.id}-dev...@li...</subscribe>
<unsubscribe>${pom.id}-use...@li...</unsubscribe>
<archive>http://sourceforge.net/mailarchive/forum.php?forum_id=11777</archive>
</mailingList>
<mailingList>
<name>Maven-Plugins Developer List</name>
<subscribe>${pom.id}-dev...@li...</subscribe>
<unsubscribe>${pom.id}-dev...@li...</unsubscribe>
<archive>http://sourceforge.net/mailarchive/forum.php?forum_id=11782</archive>
</mailingList>
<mailingList>
<name>Maven-Plugins CVS Commits List</name>
<subscribe>${pom.id}-cvs...@li...</subscribe>
<unsubscribe>${pom.id}-cvs...@li...</unsubscribe>
<archive>http://sourceforge.net/mailarchive/forum.php?forum_id=11781</archive>
</mailingList>
</mailingLists>
@@ -107,7 115,7 @@
<include>**/*Test.java</include>
</includes>
</unitTest>
-
<!-- J A R R E S O U R C E S -->
<!-- Resources that are packaged up inside the JAR file -->
|
|
From: <ste...@ya...> - 2002-09-07 11:50:54
|
Hi, The CVS commits are back, at last !! Thanks for your patience ! Stéphane ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com |
|
From: Jeff T. <jef...@us...> - 2002-09-05 10:08:15
|
On Thu, Sep 05, 2002 at 11:02:18AM +0200, Stéphane Mor wrote: > Hi, > > Sorry, the CVS commits are currently broken due to a misconfiguration. > I tried and setup the CVS commits list like the ones at Jakarta, which > failed ! Did you follow the README.txt in Jakarta's CVSROOT? It describes the process (with one omission). I wrote it :) if you need help. Otherwise just using Sourceforge's syncmail script is nice'n easy. --Jeff > Things should be fixed pretty soon I believe. > > Thanks for your patience. > Stéphane |
|
From: <ste...@ya...> - 2002-09-05 09:02:13
|
Hi, Sorry, the CVS commits are currently broken due to a misconfiguration. I tried and setup the CVS commits list like the ones at Jakarta, which failed ! Things should be fixed pretty soon I believe. Thanks for your patience. Stéphane ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com |
