Hi,
On Fri, Sep 25, 2009 at 12:06 PM, Jukka Zitting wrote:
> Please try the new build out and report any problems you encounter. If
> everything works fine, I'll proceed to JempBox and finally to PDFBox.
Given no major reported issues, I've now switched also the JempBox
build to Maven. To try it
Hi
Jukka Zitting schrieb:
> ...
> I started with the FontBox build, that is now (as of revision 818793)
> entirely Maven-based. To try out the build, use:
>
> svn co
> https://svn.apache.org/repos/asf/incubator/pdfbox/fontbox/trunk
> fontbox-trunk
> cd fontbox-trunk
> mvn clean ins
Hi,
On Thu, Sep 24, 2009 at 11:36 AM, Niall Pemberton
wrote:
> I contributed patches for the FontBox and JempBox to the following JIRA
> tickets:
Thanks!
I started with the FontBox build, that is now (as of revision 818793)
entirely Maven-based. To try out the build, use:
svn co https://s
On Thu, Sep 24, 2009 at 10:27 AM, Jukka Zitting wrote:
> Hi,
>
> On Fri, Sep 11, 2009 at 4:34 PM, Jukka Zitting
> wrote:
>> I know we've touched this subject every know and then, but I'd like to
>> bring it up again: How would people feel about switching from Ant to
>> Maven as the main PDFBox b
Hi,
On Fri, Sep 11, 2009 at 4:34 PM, Jukka Zitting wrote:
> I know we've touched this subject every know and then, but I'd like to
> bring it up again: How would people feel about switching from Ant to
> Maven as the main PDFBox build tool?
I didn't hear any big objections, so I'll move forward
This is a great example of a maven advantage.
Maven defines (universally) a set of life cycle goals. The most commonly
used are test, compile, package, and deploy (to a repository). All
dependency resolution is done automagically with nice caching, signature
checking and so on.
The advantage he
I use IntelliJ IDEA and love maven. The primary reason is that since IDEA
is the minority IDE, this gives me a usable project structure
representation. IDEA can directly important the maven pom and everything
just works. Eclipse users maintain the pom rather than eclipse specific
files.
I expec
I also am in favour of Maven integration. That would also correct the issue
where the pom.xml file was not published along with the jar file to the
maven repository for jempbox.
Y.
Life is good!
2009/9/11 Andreas Lehmkühler
> Hi,
>
> I know maven a little and ant a little bit more, but I guess
Hi,
I know maven a little and ant a little bit more, but I guess I don't
know both good enough to decide which one is the better choice. If there
are any advantages using maven, let's do it.
@Jukka
As you like to volunteer for a possible migration, have a look at
PDFBOX-499 and PDFBOX-500. They a
single command (e.g. `ant get.externallibs`).
>
> --Adam
>
>
>
>
> "Martinez, Mel"
> 09/11/2009 10:29
> Please respond to
> pdfbox-dev@incubator.apache.org
>
>
> To
> "pdfbox-dev@incubator.apache.org"
> cc
>
> Subject
> R
ease respond to
pdfbox-dev@incubator.apache.org
To
"pdfbox-dev@incubator.apache.org"
cc
Subject
RE: Using Maven in PDFBox
Maven is in its base form a command-line build tool, like Ant.
Go to http://maven.apache.org/ to find out more.
For NetBeans integration, see:
Given that PDFBox now already downloads dependencies from the net, one
of my biggest points against Maven/Ivy is already moot. Switching to
Maven now is not a big deal anymore. I still don't like builds that rely
on possibly multiple external servers (besides the ASF's SVN server) to
be online at t
12:20 PM
To: pdfbox-dev@incubator.apache.org
Subject: Re: Using Maven in PDFBox
Sounds great for eclipse users. How does maven work for people who use
Netbeans or some other IDE? Is there a readily available standalone
windows binary?
--Adam
Jukka Zitting
09/11/2009 08:42
Please respond
Subject
Re: Using Maven in PDFBox
Hi,
On Fri, Sep 11, 2009 at 5:09 PM, Martinez, Mel
wrote:
> Using Maven doesn't necessarily == improved integration with Eclipse.
Correct, you can certainly also mess things up with Maven.
What I'm thinking about is a setup like in many of the o
Hi,
On Fri, Sep 11, 2009 at 5:09 PM, Martinez, Mel wrote:
> Using Maven doesn't necessarily == improved integration with Eclipse.
Correct, you can certainly also mess things up with Maven.
What I'm thinking about is a setup like in many of the other projects
I'm actively working on (Jackrabbit,
OK. I amend my support.
+1 for correctly done maven support. -1 for doing it wrong.
On Fri, Sep 11, 2009 at 8:09 AM, Martinez, Mel wrote:
> Using Maven doesn't necessarily == improved integration with Eclipse.
--
Ted Dunning, CTO
DeepDyve
10:57 AM
To: pdfbox-dev@incubator.apache.org
Subject: Re: Using Maven in PDFBox
Having no familiarity with Maven, I hesitate ... but I'll work with whatever
those more experienced w/ Java prefer.
IDE integration would be easier ... like using Eclipse would actually become
practical? I think I c
Having no familiarity with Maven, I hesitate ... but I'll work with whatever
those more experienced w/ Java prefer.
IDE integration would be easier ... like using Eclipse would actually become
practical? I think I could handle that!
Daniel
On Fri, Sep 11, 2009 at 10:39 AM, Ted Dunning wrote:
Speaking as a consumer rather than direct contributor, I would LOVE this
switch.
On Fri, Sep 11, 2009 at 7:34 AM, Jukka Zitting wrote:
> I know we've touched this subject every know and then, but I'd like to
> bring it up again: How would people feel about switching from Ant to
> Maven as the mai
19 matches
Mail list logo
