Thanks for your feedback.
I will add the src/site thing. But in the meantime, I have these question:
Why is the source-plugin adding the target/ ?
Why is this:
build
resources
resource
directorysrc/main/resources/directory
/resource
!-- also include license and notice
Hey Martin,
is there a need that we need to have the NOTICE, LICENSE and
INCUBATOR.TXT in $basedir} ?
When moving them to src/resource/meta-inf they are in the META-INF of
the -source jar and the *real* jar.
But still not inside the javadoc-JAR. Any idea ?
-M
On 2/20/07, Matthias Wessendorf
Sources and javadoc probably don't reuse that information and to be honest I
don't know how well the
source-plugin and javadoc-plugin is configurable with this (have to dig into
this)
Mvgr,
Martin
Matthias Wessendorf wrote:
Thanks for your feedback.
I will add the src/site thing. But in
I just pinged the maven list.
Looks like the Source plugin has the javadoc jar containing the mentioned files
-M
On 2/20/07, Martin van den Bemt [EMAIL PROTECTED] wrote:
Sources and javadoc probably don't reuse that information and to be honest I
don't know how well the
source-plugin and
I don't mind having it in the the META-INF directory btw..
Mvgr,
Martin
Matthias Wessendorf wrote:
Hey Martin,
is there a need that we need to have the NOTICE, LICENSE and
INCUBATOR.TXT in $basedir} ?
When moving them to src/resource/meta-inf they are in the META-INF of
the -source jar
Ok, Martin I fixed those things
http://people.apache.org/~matzew/stage/
Once we get the approval from the Incubator PMC guys, I'd like to
test/use this tool for doing the copy:
http://docs.codehaus.org/display/MAVENUSER/Repository+Tools
-Matthias
On 2/19/07, Martin van den Bemt [EMAIL
I don't know why we couldn't have a skin repository on Trinidad
personally. If for nothing else but to provide examples to help people
skin the product.
Scott
Simon Lessard wrote:
Hmm I don't know. I would have liked to see it hosted as a new Trinidad
project, a bit like trinidad-demo so
Hi Adam
I already have trinidad working with facelets. The problem is it only
runs with trinidad as the *default rendering kit*. Defining trinidad
as the rendering kit per page does *not* work. Please see my first
mail for details.
On 2/19/07, Adam Winer [EMAIL PROTECTED] wrote:
Oh, I see.
btw. the javadoc jar issue is triggered by a bug inside of the plugin.
Martin,
do you bring the vote up to [EMAIL PROTECTED], once you voted +1 :)
Thanks,
Matthias
On 2/20/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Ok, Martin I fixed those things
http://people.apache.org/~matzew/stage/
Yep, re-reading it, that's exactly what you said. Sorry
for the misunderstanding. So this is a tougher nut
to crack. I can imagine some hacks to try to
instantiate the rendering context on the fly, but
nothing really obvious and bulletproof comes to mind.
I think we need a JIRA issue...
--
10 matches
Mail list logo
