pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roger L. Whitcomb" <Roger.Whitc...@actian.com>
Subject RE: New dependency breaks maven build
Date Tue, 28 May 2013 17:38:12 GMT
First off, the code in "trunk" I'm working on is not going to be ready
for release for some time (probably at least a month or two), so I would
expect changes on an on-going basis.  So, absolutely we won't release
Pivot 2.1 until there is a VFS release that we can use.  But, I don't
really expect to release Pivot 2.1 until close to the end of the year,
depending on what everybody thinks about the feature set, etc.


Second, since you're doing (essentially) a private branch, can I suggest
you branch from the 2.0.x branch instead of "trunk"?  As I said the code
(except for the VFS browser) is identical, so you're not going to lose
anything wrt your changes.  And then you're not going to have any
problems with unreleased Commons VFS code.  We have already started some
changes to do a 2.0.4 branch, so since you need to build your code right
now, this would probably be a more stable place to work than "trunk"
anyway....  And once we iron out the maven stuff in "trunk", you could
definitely switch at that point.  The changes you have made (I already
took a quick look) are mostly new files and a few changes to existing
ones, so I don't think it would take much effort to apply the patch to
"branches/2.0.x" instead of "trunk" anyway.


Third, there was discussion about the binary incompatibilities between
VFS 2.0 and 2.1 already.  I don't have a reference to the discussion
right in front of me, but it was their decision, well before I had any
input.... I could suggest it, but since I'm not a committer for Commons
my opinion probably wouldn't carry much weight....


And lastly, could you use the code here:
ository (esp. the <repository> stuff) to enable using the snapshot code
(if you want to continue using "trunk")?




From: Andrei Pozolotin [mailto:andrei.pozolotin@gmail.com] 
Sent: Tuesday, May 28, 2013 10:15 AM
To: Roger L. Whitcomb
Cc: dev@pivot.apache.org; David Ray
Subject: Re: New dependency breaks maven build


maven - no problem, but lets deal with commons-vfs2 dependency first

1) commons-vfs2 v 2.1-SNAPSHOT is binary incompatible with release v 2.0
they changed interfaces, etc. the version really should be 3.X.X
do you have any say in that? can you make apache commons change their
mind about version number
let them read this if they have questions why

2) I think pivot should depend only on releases.
can you make apache commons group release commons-vfs2 any time soon?
if not, can we go back to commons-vfs2 v 2.0 release?

issue at hand: we build private version of pivot with maven:

and maven does not event permit to do a release when you depend on
so with current snapshot dependency we are now totally broken :-)

-------- Original Message --------
Subject: Re: New dependency breaks maven build
From: Roger L. Whitcomb <Roger.Whitcomb@actian.com>
To: Andrei Pozolotin <andrei.pozolotin@gmail.com>
<mailto:andrei.pozolotin@gmail.com> , dev@pivot.apache.org
Cc: "David Ray" <david.ray@barchart.com> <mailto:david.ray@barchart.com>

Date: Tue 28 May 2013 11:58:27 AM CDT

	Hi Andrei,

	                Help with maven would be good.  The version I am
using (and is checked into the "wtk/lib" directory) is a pre-release
snapshot of 2.1 (version "2.1-SNAPSHOT").  Don't know if that will work
or not - I'm building Commons locally myself.  Attached is my attempt at
adding the dependency in the "pom.xml", but I'm not even getting to
first base trying to build with maven myself (i.e., it says there is
nothing to do even after doing "mvn clean", so I don't get the build
failures) .... So, any help you could give would be appreciated.



	~Roger Whitcomb


	From: Andrei Pozolotin [mailto:andrei.pozolotin@gmail.com] 
	Sent: Tuesday, May 28, 2013 9:52 AM
	To: dev@pivot.apache.org
	Cc: Roger L. Whitcomb; David Ray
	Subject: Re: New dependency breaks maven build


		Thank you for clarification. 
		Let me know if you need help with maven.
		Also, current trunk does not compile with public vfs 2.0






		which dependency are you using?

	-------- Original Message --------
	Subject: Re: New dependency breaks maven build
	From: Roger L. Whitcomb <Roger.Whitcomb@actian.com>
	To: dev@pivot.apache.org
	Cc: "David Ray" <david.ray@barchart.com>
	Date: Tue 28 May 2013 11:29:09 AM CDT

		My apologies -- I build using Ant, so I didn't check the
pom.xml.  I
		will fix this.
		I have added (the beginnings of) two new components that
duplicate the
		FileBrowser and FileBrowserSheet, but using the Commons
VFS (Virtual
		File System) so you can browse remote systems, inside
.zip and .jar
		files, etc.  At build time (in the "trunk" code) you
will need this .jar
		in order to build, and if you use the new components you
will also need
		the .jar file.  But, if you don't use the new components
you won't need
		the .jar file at runtime.
		At the moment, the code in the "branches/2.0.x" branch
is identical to
		"trunk" (actually better, because it includes a bug fix
that hasn't been
		migrated to "trunk" yet) (except that "trunk" has these
new components),
		so if you desperately need to build, I would just use
this branch
		instead until I get the Maven build working.
		~Roger Whitcomb
		-----Original Message-----
		From: Andrei Pozolotin
		Sent: Tuesday, May 28, 2013 8:46 AM
		To: dev@pivot.apache.org
		Cc: David Ray
		Subject: Re: New dependency breaks maven build
		good point. it used here:
		I am curious if it is really needed?
		-------- Original Message --------
		Subject: New dependency breaks maven build
		From: David Ray <david.ray@barchart.com>
		To: dev@pivot.apache.org
		Date: Tue 28 May 2013 10:39:35 AM CDT

			There was a dependency added to pivot-core (
org.apache.commons.vfs2 )


			that breaks the maven build I think the
dependency needs to be added

		to the pom.





  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message