FYI: In early days of M2 build the plugin did look for this string.
It changed some time before Jan 2007. All the wars here have been built
using /web-app as the inject string.
These changes are actually breaking my builds on WinXP w/ Sun 1.5.0_11 and
Maven 2.0.6 now for the Tomcat config of geronimo-welcome app.
If I remove the added configuration attributes from jspc-maven-plugin,
remove the Fragment comment from the web.xml source and use the 20070603
snapshot of
Strange, I don't understand why we're seeing inconsistent behavior
across different environments. Should be OK to go ahead and commit
your further refinements to how we invoke the plugin and then let's
keep an eye on it.
Best wishes,
Paul
On Jun 6, 2007, at 11:34 AM, Donald Woods wrote:
Donald,
If you add the configuration and the fragment comment, can you
reproduce the error? Do you see the error mentioned in this thread or a
NCDFE o.a.AnnotationProcessor.
Thanks
Anita
--- Paul McMahan [EMAIL PROTECTED] wrote:
Strange, I don't understand why we're seeing inconsistent
I'd really like to get more information on the corruption that
occurs, and what issues it has on windows. I can't see anything
obvious in the code which would cause it be have so strangely. If
you can, please tell me exactly what the plugin spits out and what
the precise corruption is...
The fragment and configuration is in the code in trunk right now, which is
causing my build failures on WinXP, but not SLED10/SLES10
The error I'm seeing, is when the CAR files are created, because the jspc
updated web.xml files have duplicate webapp entries. It seems that where
the
Can you paste me one of the corrupted web.xml files please?
--jason
On Jun 6, 2007, at 10:20 AM, Donald Woods wrote:
The fragment and configuration is in the code in trunk right now,
which is causing my build failures on WinXP, but not SLED10/SLES10
The error I'm seeing, is when the
FWIW, I am using windows XP, Sun JDK-1.5.0_11 and maven 2.0.6.
Yesterday I hit 2 problems which went away after cleaning up relevant
parts of .m2 repo (mvn-jspc-plugin and o.a.g.applications). I have not
been able to reproduce it today with or w/o inject string.
Thanks
Anita
I'd really like to
I know of four developers that hit the error, but don't understand
why everyone didn't hit it. Without the change I see the build error
reported in GERONIMO-3209. I think that the previous plugin looked
for '!-- [INSERT FRAGMENT HERE] --' by default and the new one does
not. The result
It would be interesting to know if all four error cases did a
partial build (i.e. application, config, assembly) without mvn -N from
the top directory.
Thanks
Anita
--- Paul McMahan [EMAIL PROTECTED] wrote:
I know of four developers that hit the error, but don't understand
why everyone
Why would Geronimo fail to parse an xml file with a valid xml comment?
There was a bug in the first 2.0-SNAPSHOT of the jspc-maven-plugin
which may have caused the generated web.xml to be corrupt, but I've
fixed that.
I don't believe that the previous version of the plugin defaulted the
On Jun 5, 2007, at 4:37 PM, Jason Dillon wrote:
Why would Geronimo fail to parse an xml file with a valid xml comment?
Good question. I should be able to revert locally and recreate the
error if you'd like to see some more data.
There was a bug in the first 2.0-SNAPSHOT of the
12 matches
Mail list logo
