[ http://jira.codehaus.org/browse/XDP-95?page=all ]
Diogo Bacelar Quintela updated XDP-95:
--
Version: plugin-ejb
Fix Version: plugin-ejb
> Plugin for Service-endpoint generation
> --
>
> Key: XDP-9
Hmm, I also get
org.xml.sax.SAXParseException: Document is invalid: no grammar found.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.custommonkey.xmlunit.XMLUnit.buildDocument(XMLUnit.j
Finish Deployment Descriptor ejb-jar.xml
Key: XDP-94
URL: http://jira.codehaus.org/browse/XDP-94
Project: XDoclet 2 Plugins
Type: Task
Components: ejb
Reporter: Diogo Bacelar Quintela
Assigned to: Diogo Bacelar Quintela
Paolo
See
http://jira.codehaus.org/browse/XDP-86
http://jira.codehaus.org/browse/XDP-72
I believe this is the same problem as you have.
Classpath problems.
Diogo
> Hi Guys,
> I'm in trouble with a feature I wanna add to my Tapestry plugin:
> I'd like to generate specification files only for cla
Guys,
I was adding xsd declaration to the WebPlugin, just like I did
yesterday for the TaglibPlugin. However, eventhough for none of those,
I did something like registering a dtd/xsd, I run into an issue only
with the WebPlugin, whose validation fails with the following message:
ParsingFailed DTD
Build a complete testcase set with testing of particular situations
---
Key: XDP-96
URL: http://jira.codehaus.org/browse/XDP-96
Project: XDoclet 2 Plugins
Type: Task
Reporter: Diogo Bacelar Quintela
As
[ http://jira.codehaus.org/browse/XDP-95?page=all ]
Diogo Bacelar Quintela updated XDP-95:
--
Component: ejb
> Plugin for Service-endpoint generation
> --
>
> Key: XDP-95
> URL: http://jira.codehau
Plugin for Service-endpoint generation
--
Key: XDP-95
URL: http://jira.codehaus.org/browse/XDP-95
Project: XDoclet 2 Plugins
Type: Task
Reporter: Diogo Bacelar Quintela
Assigned to: Diogo Bacelar Quintela
--
This message is
[ http://jira.codehaus.org/browse/XDP-94?page=all ]
Diogo Bacelar Quintela updated XDP-94:
--
Version: plugin-ejb
Fix Version: plugin-ejb
> Finish Deployment Descriptor ejb-jar.xml
>
>
> Key: X
[ http://jira.codehaus.org/browse/XDP-96?page=all ]
Diogo Bacelar Quintela updated XDP-96:
--
Component: ejb
> Build a complete testcase set with testing of particular situations
> ---
>
Review and complete interfaces generation
-
Key: XDP-97
URL: http://jira.codehaus.org/browse/XDP-97
Project: XDoclet 2 Plugins
Type: Task
Components: ejb
Reporter: Diogo Bacelar Quintela
Assigned to: Diogo Bacelar Quintel
[ http://jira.codehaus.org/browse/XDP-96?page=all ]
Diogo Bacelar Quintela updated XDP-96:
--
Version: plugin-ejb
Fix Version: plugin-ejb
> Build a complete testcase set with testing of particular situations
> -
[ http://jira.codehaus.org/browse/XDP-97?page=all ]
Diogo Bacelar Quintela updated XDP-97:
--
Version: plugin-ejb
Fix Version: plugin-ejb
> Review and complete interfaces generation
> -
>
> Key:
--- Paolo Donà <[EMAIL PROTECTED]> wrote:
> Hi Guys,
> I'm in trouble with a feature I wanna add to my
> Tapestry plugin:
> I'd like to generate specification files only for
> classes which implements a
> specific tapestry interface (eg.
> org.apache.tapestry.IPage) either directly
> or extend
--- Grégory Joseph <[EMAIL PROTECTED]> wrote:
> On 31/08/05, Diogo Quintela (EF)
> <[EMAIL PROTECTED]> wrote:
> >
> > | Konstantin > a release is fine with me, but I'm
> a bit concerned about
> > the
> > | new jelly dependencies - the web plugin doesn't
> work anymore if we use
> > 1.0
> >
>
Hi Guys,I'm in trouble with a feature I wanna add to my Tapestry plugin:I'd
like to generate specification files only for classes which implements
a specific tapestry interface (eg. org.apache.tapestry.IPage) either
directly or extending some implementing base class, so I implemented
the shouldGene
On 31/08/05, Diogo Quintela (EF) <[EMAIL PROTECTED]> wrote:
| Konstantin > a release is fine with me, but I'm a bit concerned about the| new jelly dependencies - the web plugin doesn't work anymore if we use 1.0Greg, replaceNamespaces was a tag that I contributed into jelly-xml.
The new jelly versi
Hi, Paolo.
How many time do you need to finish Tapestry plugin??
If you think that takes day or so then it worth to wait a little with release.On 8/31/05, Paolo Donà <[EMAIL PROTECTED]
> wrote:Sorry guys,I feel really newbie in here...Are you going to release the
1.0.2 ?I feel I won't be able to
| Konstantin > a release is fine with me, but I'm a bit concerned about the
| new jelly dependencies - the web plugin doesn't work anymore if we use 1.0
Greg, replaceNamespaces was a tag that I contributed into jelly-xml.
The new jelly versions support usage of xml with namespaces (that was far
i
PS: Greg, btw, Are you working in windows??
MacOsX mostly , and Linux at work.
About the xml api's, it seems they differ from jdk to jdk, even betwen
1.4 and 1.5, which is maybe one of the reasons we've had issues? I'm
working with 1.5 by default on all my machines now.
Konstantin > a release is f
--- Paolo Donà <[EMAIL PROTECTED]> wrote:
> Sorry guys,
> I feel really newbie in here...
> Are you going to release the 1.0.2 ?
> I feel I won't be able to finish the tap-plugin by
> tonight.. I'm
> buried at work right now.
OK, I can do it tomorrow morning.
regards,
[ Konstantin Pri
Sorry guys,
I feel really newbie in here...
Are you going to release the 1.0.2 ?
I feel I won't be able to finish the tap-plugin by tonight.. I'm
buried at work right now.
Paolo
On 8/31/05, Anatol Pomozov <[EMAIL PROTECTED]> wrote:
>
> > 2ALL:
> >
> > OK, now we know that there is no build pro
> I restored old dependencies and everything started to
> work again.
You mean they will be added to project.xml? In generama and xdoclet-plugins?
> OK, now we know that there is no build problem,
> Everybody happy with release tonight?
I am OK on this :)
I'll try no to commit nothing tonight
--- "Diogo Quintela (EF)" <[EMAIL PROTECTED]>
wrote:
> > > > DId you got my logs? ( off-list )
> > >
> > > I did. I deleted my maven repository (eheh.. I
> > > renamed) to force redownload,
> > > and did a clean rebuild. "BUILD SUCCESSFUL"
> >
> > Well, zapping repository did not help. Then
2ALL:OK, now we know that there is no build problem,Everybody happy with release tonight?
Yeah, Kostja, c'mon. Lets make a rock'n'roll.
-- anatol
> > > DId you got my logs? ( off-list )
> >
> > I did. I deleted my maven repository (eheh.. I
> > renamed) to force redownload,
> > and did a clean rebuild. "BUILD SUCCESSFUL"
>
> Well, zapping repository did not help. Then it must
> be xml parser issue... Shall we ad explicit
> dependency to
26 matches
Mail list logo
