|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 20
Messages: 20
Messages: 20
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Have you tried to search a big ANT script to track dependent targets?
The name of the ANT GUI development tool is Antodyne. ANT considered to be a great language for the build scripts. ANT tasks encapsulate and parameterize corresponding functions, but the latest releases of ANT introduce a large number of tasks that is hard to memorize.
Utilizing dependencies approach, targets can be constructed into an extensive execution tree, however have you tried to search through a big ANT script to track dependent targets?
Sometimes it seems to be overwhelming. It can't be easy to figure out a property value when it is nested with other properties. That is when Antodyne comes in. Find a full tool description here http://www.goaldreen.com/products
Message was edited by: jvaughan@techtarget.com
|
|
|
Message #329048
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Have you tried to search a big ANT script to track dependent targets?
The first rule of writing maintainable ant scripts is to *never* use the depends attribute. It's unfortunate that it was ever included in ant in the first place, more unfortunate that it seems to be used in every example ant script, and even more unfortunate that it has contaminated a much better build system known as gradle). Stop the insanity!
As for the product mentioned above, I have no opinion since I've never tried it. However, my first recommendation for improving your build experience would be to move off of ant.
|
|
|
Message #329049
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Have you tried to search a big ANT script to track dependent targets?
Even I vouch for Maven.
|
|
|
Message #329050
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: one word
Maven. I had to say it.
Every time a person runs a Maven build, a mammal is sacrificed.
|
|
|
Message #329052
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: one word
<Every time a person runs a Maven build, a mammal is sacrificed.> I don't get your point. Why?
|
|
|
Message #329053
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: one word
Maven. I had to say it. I also prefer maven than ant, but it'll better if I can find a maven repository for the oracle ojdbc driver.
|
|
|
Message #329055
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Negative Feelings Toward Maven
<Every time a person runs a Maven build, a mammal is sacrificed.> I don't get your point. Why?
Probably for two reasons. First, if a project follows Maven's conventions and expected structure, it can work quite well. However, if it doesn't, it is likely to turn into a total mess. Second, although this may not be Maven's fault, I don't think I've ever encountered a Maven build that ran successfully the first time. This is probably the fault of the person who set up the build, but it makes for a very discouraging experience.
--Matt
The Software Grove
|
|
|
Message #329058
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Looks like an advertisement
I went to their website and downloaded their product description. It provides an extremely tedious user interface to build an Ant file. They want money for this application. There are several apps that already do similar things and for free. See http://ant.apache.org/projects.html for a good list. Once again, it looks like TheServerSide is posting advertisements rather than articles.
|
|
|
Message #329071
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: maven repo for oracle driver
Maven + Nexus is the optimal solution: you have a project management tool with a libraries repository under your complete control.
You can deploy your own artifact (for example oracle's libraries if some thing is not present) within 2 minutes.
I don't understand why people search "alternatives" to Maven:
in the most cases the alternatives are very similar to the original one; so why?
Moreover if Maven is complicated or ugly, there is a good Open Source alternative: Apache Ivy, it's free and very easy to use (Ivy is an Ant sub project).
|
|
|
Message #329072
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: maven repo for oracle driver
Go to http://repository.sonatype.org/ and type in ojdbc in the search box.
Also, you can do something like this:
1. Add inner local repo reference to pom.xml:
<pluginRepository>
<id>local</id>
<url>file://lib</url>
</pluginRepository>
2. Put any artifacts which you can't find in any public repository to your local repository inside project structure according to Maven directory convention, for example:
<project_home>\lib\com\oracle\ojdbc14\10.2.0.2.0\ojdbc14-10.2.0.2.0.jar
3. PROFIT.
|
|
|
Message #329094
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
I have the opposite experience
I work with many large clients with many very large projects, and as a rule the Maven projects (even those with hundreds of thousands of lines of code and dozens of modules) run without a hitch, and are relatively easy to maintain and evolve. The ant scripts, on the other hand, are maintenance nightmares. In large organizations, the standardization offered by Maven is a *HUGE* benefit.
|
|
|
Message #329095
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
No no no and NO!
The file:// strategy described above is a recipe for non-portable build scripts - to be avoided at all costs! Just deploy the Oracle JAR to your enterprise repository, it's that simple.
|
|
|
Message #329102
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: No no no and NO!
The file:// strategy described above is a recipe for non-portable build scripts - to be avoided at all costs! Just deploy the Oracle JAR to your enterprise repository, it's that simple.
Absolutely wrong statement.
Strategy, described above is the best recipe to create fully-portable build scripts.
The trick is that "lib" folder should be a part of source code (<project_home>/trunk/lib for example), and it should be committed into source control system. In that case, you even don't need to deploy any jars to your enterprise repository (by the way, not all companies has such separate repositories), all users will automatically get specific jars to their local repository after first Maven build execution.
Also, this approach doesn't require any additional activities from build integrator.
|
|
|
Message #329113
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Negative Feelings Toward Maven
<Every time a person runs a Maven build, a mammal is sacrificed.> I don't get your point. Why?
Probably for two reasons. First, if a project follows Maven's conventions and expected structure, it can work quite well. However, if it doesn't, it is likely to turn into a total mess. Second, although this may not be Maven's fault, I don't think I've ever encountered a Maven build that ran successfully the first time. This is probably the fault of the person who set up the build, but it makes for a very discouraging experience.
--Matt
The Software Grove
Gotta love it when pro maven people dismiss real issues as user error. Plenty people setup maven based on "the recommended" conventions and it still sucks.
My bias opinion, maven is a special kind of torture for masochists. Ant works perfectly fine without all the stupid guard rails and idiocy of maven. Flame on!
|
|
|
Message #329122
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Negative Feelings Toward Maven
Probably for two reasons. First, if a project follows Maven's conventions and expected structure, it can work quite well. However, if it doesn't, it is likely to turn into a total mess. Second, although this may not be Maven's fault, I don't think I've ever encountered a Maven build that ran successfully the first time. This is probably the fault of the person who set up the build, but it makes for a very discouraging experience.
--Matt
The Software Grove
Gotta love it when pro maven people dismiss real issues as user error. Plenty people setup maven based on "the recommended" conventions and it still sucks.
My bias opinion, maven is a special kind of torture for masochists. Ant works perfectly fine without all the stupid guard rails and idiocy of maven. Flame on!
What about "total mess" and "I don't think I've ever encountered a Maven build that ran successfully the first time" makes you think I'm "pro maven"? I was politely trying to explain to someone who did sound pro maven that others, including myself, have found it a pain to deal with. I theorized that part of that might be a failure in understanding on the part of the person putting together the build, but the fact that Maven seems to confuse a lot of smart people is certainly not an argument in its favor.
In another recent thread, I suggested that people check out Gradle before deciding to use Groovy in conjunction with Maven.
--Matt
|
|
|
Message #329154
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Negative Feelings Toward Maven
Iam going to bite.
You do not understand Maven
User inexperience or plain stupidity is the fault that maven build does not run on your first try.
If you want a structure different from Maven, then you are throwing the best practice/experience down the drain of numerous veterans of java development.
There is absolutely no need to use a different structure opposed to the maven suggested one. If you do, you are making it unnecessarily difficult for yourself and the team.
If you persist in using ant, good luck debugging ant scripts, maintaining them etc. But you won't make my team. i want to build software, not repair broken ant scripts all the time.
Enough flame for now. Welcome to the forum dino. :)
|
|
|
Message #329156
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
iVy is not Maven
Ivy is not equal to Maven by a long shot. Ivy is only a dependency manager, whilst Maven is a life cycle tool of which dependency management is only 1 element.
Furthermore. why use Ivy when you have Maven. Have not found a project yet, that i needed to use Ivy. If you have such a complex structure, you should reconsider your set up and simplify it.
|
|
|
Message #329157
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Negative Feelings Toward Maven
@M. Lin
Eclipse, Itellij, jdeveloper... all use their own suggestion of a java structure. Most try to mimic the jee setup.
Maven also suggest a structure.
As in all of these tools you can use your own. BUT beware of the consequences. if you develop in a team, then using your own quirky way is not appreciated. I with my co-workers can startup blindly by retrieving the source from the repo and for example compile mvn compile.
No configuring whatsoever.
I have seen many projects using ant that really suck when you want to get started. minimun 1/2 day to get going due to incomprehensible undocumented ant scripts with lots of localized configuration
|
|
|
Message #329278
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Negative Feelings Toward Maven
If you persist in using ant, good luck debugging ant scripts,
At least for ant, there exists a debugger.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
In this session Nati Shalom demonstrates how to take a standard Java EE web application and scale it out or down dynamically without changes to the application code. Seeing as most web applications are over-provisioned to meet infrequent peak loads, this is a dramatic change because it enables growing your application as needed, when needed, without paying for unutilized resources.
(May 19, Tech Talk)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
