May I add, based from the currently deployed site, the first page you
get after clicking the plugin name, is
Project Info -> About
which is a replica of the page
Project Reports -> Plugin documentation
just fyi
Pete Marvin King wrote:
I think it's a good idea to be able to pull
Issue Subscription
Filter: Design & Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
If it slows down the build, people will turn it off forcably/complain,
etc too.
We can enable the profile for CI and deployment, which might make it
better. WDYT?
However, I don't know if this should be a "deployment failure" type
issue - I'd be happy with daily nags on it.
- Brett
On 23/
My (limited) experience tells me that if you don't enforce it you
don't get it done
If it's in a profile I can deploy it and then continuum will fail and
somebody will have to chase me and tell me and then I'd have to fix
it, which means that the turnaround is pretty big.
I just added now the du
Thanks Carlos!
On 23/06/2006 7:54 AM, Carlos Sanchez wrote:
Please note that I have brought back the maven 1 to maven 2 conversion
tools
For those interested (and with access ;) )
/home/maven/components/maven-meeper/src/bin/repoclean/sync-repoclean.sh
will run repoclean (translate from m1 to
So, you'll fix all duplications when you change the parent?
I still believe this should be in a profile used by CI. The standard
build doesn't need to worry about this.
- Brett
On 23/06/2006 1:18 AM, Carlos Sanchez wrote:
That's the point, don't accept files with duplications. Better enforce
Please note that I have brought back the maven 1 to maven 2 conversion tools
For those interested (and with access ;) )
/home/maven/components/maven-meeper/src/bin/repoclean/sync-repoclean.sh
will run repoclean (translate from m1 to m2) and put the result into
~/repository-staging/to-ibiblio/mav
That's the point, don't accept files with duplications. Better enforce
it proactively.
On 6/22/06, Brett Porter <[EMAIL PROTECTED]> wrote:
On 22/06/2006 10:27 AM, [EMAIL PROTECTED] wrote:
> Author: carlos
> Date: Wed Jun 21 17:27:49 2006
> New Revision: 416184
>
> URL: http://svn.apache.org/view
I think it's a good idea to be able to pull out the Project Document
to the top-level menus.
Currently it's hidden under Project Reports. The usual way to include
it on the site
descriptor is through ${reports}, maybe Project Documentation can have
its own
"macro definition?" like ${gener
Hello!
I'm working on Maven plugin for building project using 3rd party tools.
Problem:
My plugin (PLUGIN) is used to build project (PROJECT).
When building PROJECT my PLUGIN need to use RESOURCES (file skeletons,
etc) .
I want the RESOURCES to be in separate artifact refered from PLUGIN.
Reas
On Wed, 21 Jun 2006, Brett Porter wrote:
+1 IF the file permissions work when deploying.
If your umask is say 077 the files are rw---.
It used to work though, but it seems the server section is not read from
the settings.xml anymore - can someone verify this with the
proposed release version p
11 matches
Mail list logo
