On 11/19/05, Srepfler Srgjan <[EMAIL PROTECTED]> wrote:
> Hello, Mr. Raible,
> I've tried to generate hbm files from your model (appfuse) in a mockup
> maven2 project, but I haven't been too successfull; Have you managed to
> make a working m2 pom file for you appfuse project?

No.

> Do you generate hbm files via the xdoclet plugin?

No, I still use Ant for AppFuse and plan to for the next release or
two.  I might integrate M2 someday, but it's probably going to take
quite a bit of work.  I have grandious plans of someday being able to
do "mvn appfuse", but that's probably quite a ways off. ;-)

Matt

>
> Srgjan Srepfler
>
> Matt Raible wrote:
>
> >I've been using Spring 1.2.5 in my project for the past couple of
> >weeks.  The transitive dependencies feature of M2 has seemed to work
> >great b/c there were no dependencies for Spring.
> >
> >         <dependency>
> >            <artifactId>spring</artifactId>
> >            <groupId>org.springframework</groupId>
> >            <version>1.2.5</version>
> >        </dependency>
> >
> >However, as of today (possibly earlier, since I just deleted my local
> >repo this morning), I now have to exclude a whole bunch of
> >dependencies.  Below is a list of ones I had to exclude just for M2 to
> >download everything and run "mvn test". To really clean this up and
> >prevent a bunch of unused JARs in my project, it's likely I'd have to
> >greatly expand this list to include quartz, freemarker, velocity, etc.
> >
> >(more comments after the xml below)
> >
> >         <dependency>
> >            <artifactId>spring</artifactId>
> >            <groupId>org.springframework</groupId>
> >            <version>1.2.5</version>
> >            <exclusions>
> >                <exclusion>
> >                    <artifactId>activation</artifactId>
> >                    <groupId>javax.activation</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>mail</artifactId>
> >                    <groupId>javax.mail</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>toplink-api</artifactId>
> >                    <groupId>com.oracle</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>ejb</artifactId>
> >                    <groupId>javax.persistence</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>ejb</artifactId>
> >                    <groupId>javax.ejb</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>jta</artifactId>
> >                    <groupId>javax.transaction</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>connector</artifactId>
> >                    <groupId>javax.resource</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>jaxrpc</artifactId>
> >                    <groupId>javax.xml</groupId>
> >                </exclusion>
> >                <exclusion>
> >                    <artifactId>jms</artifactId>
> >                    <groupId>javax.jms</groupId>
> >                </exclusion>
> >            </exclusions>
> >        </dependency>
> >
> >Since spring.jar only depends on commons-logging, shouldn't the rest
> >of these be marked optional?  How did this change in the last couple
> >of days - did someone upload a new POM for Spring to ibiblio?
> >
> >Thanks,
> >
> >Matt
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to